Hi,
When we push our main package on dev environment to test environment, DCMs (Lead and opportunity) only partially update.
We binded the SysDcmSettings as well as SysDcmSchemaInSettings in the package, new stages get added to the DCM however, stages for which name have changed or been removed/replaced with another stage do not update.
Any idea what could be happening ?
Like
Hi,
You need to check if the SysDcmSchemaInSettings and SysDcmSettings is connected properly to the package. To check it you need to:
1) Execute the following SQL query (if you are using PostgreSQL, then you need to replace square brackets with quotes):
SELECT [SysDcmSettingsId], [SysDcmSchemaUId] FROM [SysDcmSchemaInSettings] WHERE [SysDcmSchemaUId] = '8d628f2a-7941-42f3-98dd-aed0b6b708fc'where 8d628f2a-7941-42f3-98dd-aed0b6b708fc is the UId of the SysSchema record for this DCM (can be also retrieved from the URL bar of the browser when the DCM wizard is opened):
2) Make sure that there are SysDcmSchemaInSettings and SysDcmSettings bindings present in your package with the following data bound:
--SysDcmSettings
--SysDcmSchemaInSettings
In my example above these settings were saved for the DCM in the "Orders" section created by "Order status" column.
3) Once the package is deployed only changes in the DCM structure will be saved. But if you renamed some stages in the dev app - they won't be renamed in the target app.
To transfer updated names for stages you will need to perform an export/import of translations. For example, order stages can be found in the "Translations" section using the following filter by "Key" column: %Data:OrderStatus.Name%
So the final action that should be performed after the package installation is transferring of translations (using an import of translations into the "Translations" object of the target app from the excel file that was formed as a result of the export of translations from the dev app).
Using this approach everything should be transferred properly.
Best regards,
Oscar
Oscar Dylan,
HI Oscar,
Thanks a lot, it seems I have translation issues indeed. However, it is a nightmare to work the with translation section in Creatio - it takes hours and hours to load and any mishap makes the section reload completely again, which is just not feasible work in a day..... This is something Creatio really needs to improve on ...
The quickest solution I found was to connect once in english, load lookup, set column view to show the fields' ID, take a screenshot. Switch profile to French, go back to dcm stages lookup, view fields ID to make sure I'll match with the right fields in english, rename there.
Damien Collot,
Yes, sometimes the translations section needs much time to load. And sometimes it helps to run the actualization process separately (in this case the translations section opens faster). You can go to configurations, find the TranslationActualizationProcess, open it and run the process. Wait until it's completed and then try going to the translations section.
Also yes, you are correct, you can also rename values in the localization needed for the translation to be applied, but I am not sure if it will transfer the translation in such a case. Using the translations export\import works like a clock, but if you tested the approach with renaming under the French user profile and installing the package after that - perfect, then we have two options now:)
Best regards,
Oscar