dont know how but let say I have option of "ABC company" to get translated in Chinese but dont want to create a new Account record for same company so that all the transaction remains under one single customer record.
What is best practice in this scenario, do people always create a duplicate record.
CHinese user want to create everything in chinese and Englisg user want to create everything in English for same record as far as sub objects is concern ex. Contact, address, orders, opportunity, phone number
1 answer
To search the actual data in different languages, you would need to store the translated value in custom fields. Most organizations decide on a primary language for their data storaged/use. And translate the field labels and SFDC UI for different User languages. The reason for this decision is actually supported by your use case: Users can enter different languages but you want it on the same record. How would an English speaking User know what the Chinese Account Name was to make sure they were on the right record?
Also think about how someone in a CFO position (for example) would be able to create and understand reports if the data was in many languages. How would s/he be able to sort by Account Name (since ABC and XYZ are really the same Account just in different languages).
