Personlization on choice fields in CI-J only return english

(3) Share

Report

Posted on by CU03091316-0

170

When using choice fields to display dynamic text in emails in CI-J, it is only possible to show the english values in the choice fields. We are running in norwegian and want to display the norwegian values. For instance, telling someone their membership status in a mail with the wrong language for that looks very unprofessional. Does anyone know when Microsoft will improve this feature so it works properly? I have not seen anything in the wave for the next 6 months about this.

Categories:

Dynamics 365 Customer Insights - Journeys

I have the same question (0)

All responses (2)

Answers (2)

Verified answer

Saif Ali Sabri 2,351 Super User 2025 Season 2 on at

Like (0)

Report
Currently, Customer Insights - Journeys (CI-J) only supports English values when using choice fields in dynamic email content. This is a known limitation, as multilingual support for choice field values is not yet fully implemented in outbound marketing emails. Since there is no official update in the Microsoft release waves for the next six months, a workaround is required.
Workaround Solution
To ensure the correct language is displayed, you can use a custom lookup table or Power Automate to map and insert the appropriate values dynamically.
Option 1: Use a Custom Field for Translated Values

Create a new custom field in Dataverse (e.g., MembershipStatus_Norwegian).

Use a workflow or Power Automate to populate this field based on the selected choice field value.

In the CI-J email, reference the custom field instead of the default choice field.

Option 2: Power Automate to Dynamically Replace Values

Trigger Power Automate when an email is about to be sent.

Retrieve the choice field value and match it to a translation stored in a Dataverse table.

Update a separate field with the translated value before sending the email.

Use this translated field in the email template.

Option 3: Use Liquid Code (Advanced Approach)
If your emails support Liquid templates, you can create a manual mapping in Liquid.
Example:
liquid

{% case contact.membership_status %} {% when 'Active' %} Aktiv {% when 'Inactive' %} Inaktiv {% else %} Ukjent {% endcase %}

This ensures that the correct localized text appears in the email.
Microsoft Roadmap & Future Enhancements
As of now, Microsoft has not officially announced support for multilingual choice field values in CI-J emails. To push for a fix:

Submit feedback via the Microsoft Ideas portal: https://experience.dynamics.com/ideas/

Check Microsoft Release Plans regularly for updates: https://learn.microsoft.com/en-us/dynamics365/release-plans/

Conclusion
Until Microsoft provides an official fix, using custom fields, Power Automate, or Liquid can ensure your emails display the correct language.

Was this reply helpful? Yes No
Verified answer

Daivat Vartak (v-9d... 7,835 Super User 2025 Season 2 on at

Like (1)

Report
Hello CU03091316-0,

You've accurately identified a critical limitation in Dynamics 365 Customer Insights - Journeys (CIJ) regarding the handling of localized choice field values in email content. Currently, CIJ only displays the English values, which is a significant issue for organizations operating in multilingual environments like yours (Norwegian).

Unfortunately, you're also correct in your observation that Microsoft hasn't publicly announced any immediate plans to address this in the upcoming release waves (at least within the next 6 months).

Here's a breakdown of the situation and potential workarounds:

Understanding the Problem:

Choice Field Localization: Dynamics 365 supports localized choice field values, allowing you to define labels in multiple languages.

CIJ Email Rendering: CIJ's email rendering engine currently only retrieves and displays the English values, regardless of the recipient's language preferences or the email's language settings.

Impact on User Experience: This results in a poor user experience, as recipients see incorrect language values in their emails.

Workarounds (Limited and Not Ideal):

Manual Language Mapping:

Concept: Create a custom entity or a set of static variables to store the language mappings for your choice field values.

Implementation:

Create a custom entity with fields for "English Value," "Norwegian Value," etc.

Populate the entity with the corresponding language values for your choice fields.

Use JavaScript or Power Automate to retrieve the appropriate language value based on the recipient's language preferences.

Insert the retrieved value into the email content using dynamic content.

Limitations:

Very time-consuming to set up and maintain.

Not scalable for a large number of choice fields or languages.

Requires custom development.

Liquid Templating (Advanced):

Concept: Use Liquid templating within CIJ emails to implement custom logic for language mapping.

Implementation:

Use Liquid's if or case statements to check the recipient's language preference.

Based on the language, output the corresponding localized choice field value.

Limitations:

Requires advanced Liquid templating knowledge.

Can become complex to manage.

Still requires you to manually maintain the translations within the liquid code.

Power Automate for Email Content Generation (Complex):

Concept: Generate the email content entirely within Power Automate, using custom logic to retrieve and insert the localized choice field values.

Implementation:

Create a Power Automate flow that retrieves the necessary data, including the localized choice field values.

Use conditional logic to generate the email content in the appropriate language.

Send the email using the "Send an email (V2)" action.

Limitations:

Very complex to implement.

Removes the ability to use CIJ's email designer.

Requires significant Power Automate development.

Recommendations:

Provide Feedback to Microsoft:

Submit a feature request through the Microsoft Ideas portal, clearly outlining the issue and its impact.

Emphasize the importance of localized choice field values for multilingual organizations.

Contact Microsoft Support to report the issue and request an update on their roadmap.

Monitor Microsoft Documentation:

Keep a close eye on Microsoft's official documentation and release notes for any updates regarding this feature.

Plan for Future Updates:

Since the workarounds are not ideal, it is best to plan for future updates from Microsoft.

Try to design your emails, so that the impact of the english language is minimal.

In summary, the lack of localized choice field support in CIJ is a significant limitation. While workarounds exist, they are complex and not ideal. The best course of action is to provide feedback to Microsoft and monitor their documentation for updates.

If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more. If you have further questions, please feel free to contact me.

My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics 365 query.

Regards,

Daivat Vartak

Was this reply helpful? Yes No

Join the conversation

Community site session details

Personlization on choice fields in CI-J only return english

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates

Community site session details

Personlization on choice fields in CI-J only return english

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates