cancel
Showing results for 
Search instead for 
Did you mean: 

Enable translations for referential entities

Author Name: Henry Jammes

In most international projects, there is a need for translations for referential data.

Typical Business Case: need a list of Countries, with their ISO Code, Telephone Prefix, ISO Abbreviations, etc.

Option-sets are *not enough* as we cannot set any additional property on an option-set, as we would on a custom entity.
Furthermore, when integrating with a third party IS, we often do data transfers and option-sets are not appropriate.
For example, w often need to integrate referential data from SAP (countries, payment terms... etc.) that can't be natively properly translated in Dynamics CRM.

My suggestion:
=> Enable translation of the primary field (text field) of entities that are used for referential purposes.

I guess this could be achieved similarly to what you did for products.

Status: Planned

Thank you for your feedback. This is a great suggestion! We will consider this in our roadmap.

 

Sincerely,

Mike Carter

PM, Microsoft 

Comments
D365Ideas_Admin
Regular Visitor
Status changed to: Planned

Thank you for your feedback. This is a great suggestion! We will consider this in our roadmap.

 

Sincerely,

Mike Carter

PM, Microsoft 

philipverlinden
Regular Visitor
I have had similar requests from customers on small and larger implementations... so +1 from me!
carterbarry88
Advocate I

Definitely agreed with this requirement. One potential workaround that I thought about for this is to use the Product list and add custom attributes as required. You can have a "reference data" type and hide/show the applicable attributes as needed.

 

The products list can be translated so this might help in the meantime. Unfortunately, it does mean that you have to use the same entity for multiple purposes, which gets confusing.

 

Ideally, we should be able to create a reference data entity with the same translation capability as the products list.