![]() ![]() Gearset solves this problem by making each translated string individually selectable and deployable. This often failed if the language had a translated string for a component that didn't exist in the target or if only some of the translated strings in the org had been reviewed and were ready for deployment. Historically, one of the issues with deploying translations on Salesforce was that you had to deploy all the translated strings for a given language at the same time. What do translations look like in the comparison results? You will see the transitions for your prompt listed in the results as a translations component. If you need to deploy translations for a prompt you will need to include the prompt metadata type, custom labels and translations. These are also included in the Default comparison filter. Gearset will compare your custom label translation settings if custom labels and translations are both selected in your metadata comparison filter. ![]() They are included in the Default comparison filter, or you can create your own custom metadata filter. Gearset will compare your custom field translation settings if Custom object translation and Custom object are both selected in your metadata comparison filter. How do I include translations in my comparison? Translations are one of those parts of Salesforce that people really struggle to deploy and with good reason - they're a pain and come from the earliest days of the platform. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |