If you want to have reports and information in your database in two languages, e.g. your Danish and English there are two approaches you can choose from.
Both have advantages and disadvantages that are listed below:
1) Use standard Entry / "Name" fields
Add both languages in the "Name" or the Object/Activity/Budget Account etc. by separating them with a # or |
Then use Split Operators in templates. For the main one (e.g. Danish) use before split, for the English use after split.
Danish | English: Redigering | Editing OR Redigering # Editing
Good split is # or |
- also allows to search on the other languages name in object browser (e.g. used in Budgeting)
- easy to apply to templates with only one String Operator (Split on # and display the first or second element)
- Easier to update names with export/import
- Names can get very long
2) Use an Object Custom field
In Object Manager > Menu > Setup Custom Fields, add a field to the corresponding Object Custom Field template; e.g. "English Description".
Keep the Danish (Main Language) naming in all the main fields like Object Names, Activities, Budget Categories/Accounts, Custom Fields etc.
- Custom Fields are not available on Activities
- Cannot search for Object Custom field name in Object Browser
- Easily display the corresponding Custom Field in template (if available); no string operators needed