Last week, David J. was asking to the MVP list how to get more accurate data when comes the time to translate CRM customizations. His concern was to get contextual information about the terms to translate. I can only agree with him… When exporting translations, you just get an ID and the term to translate. You don’t know where it is used…
So my next tool will be a tool that exports data to translate, but with contextual information. The tool will of course be able to import these data back to the CRM application. Export and import will be managed in a supported way using web services only.
What will be included
- Entity names and descriptions
- Attribute name and description
- Boolean, Picklist, State and Status OptionSet Attribute labels
- View name and description
- Form name and description
- Form Tabs name
- Form Section name
- Form Field name
All these items have been tested successfully on UR12 organization. I still need to check if new forms are structured in the same way than classic forms. And I have to manage Global optionsets but I know it will be easy.
The export will produce an Excel workbook with multiples sheets
Each sheet will have its own columns (see Form tabs example below)
I don’t have one yet. The export/import engine is almost finished but I need to develop the UI too. And I’m on holidays tomorrow for three weeks so I won’t touch a keyboard during this time (well, almost) so I assume the tool will be ready by the end of July.