web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

🚀 Season of Sharing Community Challenge Launch!
Ask A Community Pro
Introducing our New Video Series: Community Spotlight
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / CIJ RTM Email custom c...
Customer experience | Sales, Customer Insights,...
Answered

CIJ RTM Email custom code in HTML

(2) ShareShare
ReportReport
Posted on by WD-02041034-0 4
i have a problem where i'm pasting into HTML some custom code to show/ hide content based on a recipients contact record attribute (sample below), this is erroring in the email, this does works in other platforms and believe this worked in outbound also.  i have large emails with varying content based on this attribute (some have 40+ conditions) 
 
{{#if (eq contact.xxx_subjectareaofinterest1id 'Acting and Drama')}}
----content----
{{else if (eq contact.xxx_subjectareaofinterest1id 'Criminology')}}    
----content----
 
to get around this i have to find and replace the custom code in the HTML with CIJ's Inline Conditions which turn the code into something like this (annoyingly this isn't then stored as a list for use in future emails).
 
{{#if acting}}
...
{{/if}}
 
Anyone have a solution to making my custom code work and avoiding the use of the inline conditions?
 
Thanks in advance! 
Categories:
Dynamics 365 Customer Insights - Journeys
I have the same question (0)
  • Suggested answer
    Holly Huffman Profile Picture
    Holly Huffman 6,554 Super User 2026 Season 1 on at
    Good morning, afternoon, or evening - depending on your location :)
    Hope you are well today!
     
    It seems like you're encountering a limitation with CIJ (Customer Insights - Journeys) when trying to use custom conditional logic in your email HTML. Unfortunately, CIJ's real-time marketing emails don't natively support the kind of complex conditional logic you're trying to implement. Instead, they rely on their own inline conditions, which, as you've noted, can be cumbersome for managing large emails with many conditions.
    Here are a few potential workarounds to consider:
     
    1. Preprocess the HTML:
      • Use an external tool or script to preprocess your HTML before pasting it into CIJ. This tool could take your custom conditional logic and convert it into CIJ-compatible inline conditions automatically. While this adds a step to your workflow, it could save time in the long run.
    2. Leverage Dynamic Content:
      • CIJ supports dynamic content and personalization. You might be able to restructure your email to use dynamic content blocks instead of complex conditional logic. This approach could simplify your email design and make it easier to manage.
    3. Feedback to Microsoft:
      • If this is a recurring issue, consider providing feedback to Microsoft. They may be able to enhance CIJ's capabilities in future updates to better support advanced use cases like yours.
    4. Explore Third-Party Tools:
      • If CIJ's limitations are a significant roadblock, you might explore third-party email marketing tools that better support your requirements. Some tools offer more robust support for custom HTML and conditional logic.
     
    Hope this helps :)
  • Verified answer
    Daivat Vartak (v-9davar) Profile Picture
    Daivat Vartak (v-9d... 7,847 Moderator on at
    Hello WD-02041034-0,
     

    You've encountered a common issue when transitioning from Outbound Marketing to Real-Time Journeys (CIJ/RTM) regarding custom Handlebars expressions in email HTML. While your code works in other platforms and potentially in OBM, RTM has stricter parsing and processing of Handlebars expressions, particularly around complex comparisons and lookups.

    Here's a breakdown of the problem and potential solutions:

    Understanding the Problem:

    • RTM Handlebars Limitations:

      • RTM's Handlebars implementation might have limitations or stricter rules compared to other platforms.
      • Directly comparing GUIDs (like contact.xxx_subjectareaofinterest1id) with string literals ('Acting and Drama') can cause parsing errors.
      • RTM's processing of nested if and else if statements with complex comparisons can be less tolerant. 

    • Inline Conditions (CIJ):

      • CIJ's Inline Conditions transform your code into simpler Handlebars expressions that RTM can handle.
      • However, they are not reusable as a list, which adds to the work load. 

    • Data Type Mismatch:

      • The most likely issue is that the type of data that is stored in the contact.xxx_subjectareaofinterest1id is not a string, but a GUID. Therefore a direct string comparison will fail.  

      •  

    Solutions:

    1. Use GUID Comparison (Recommended):

      • Concept:

        • Instead of comparing the GUID with a string literal, compare it with the actual GUID value.
        • You'll need to retrieve the GUID of the "Acting and Drama" and "Criminology" options from your Dynamics 365 environment. 

      • Steps:

        1. Retrieve GUIDs:

           

          • In Dynamics 365, go to the option set (lookup) field "xxx_subjectareaofinterest1id".
          • Find the GUID values for "Acting and Drama" and "Criminology".

        2. Modify Handlebars Code:

          • Replace the string literals with the actual GUID values in your Handlebars code.

          • Example:

          • {{#if (eq contact.xxx_subjectareaofinterest1id 'YOUR_ACTING_AND_DRAMA_GUID')}}

          ----content----
          {{else if (eq contact.xxx_subjectareaofinterest1id 'YOUR_CRIMINOLOGY_GUID')}}
          ----content----
          • {{/if}}

            •  
           

          • Replace YOUR_ACTING_AND_DRAMA_GUID and YOUR_CRIMINOLOGY_GUID with the actual GUID values. 
           

      • Advantages:

         

        • Ensures accurate comparison of GUID values.
        • More reliable in RTM.

      • Disadvantages:

           
        • Requires retrieving GUID values from Dynamics 365.
        • GUIDs are not user-friendly.

          •  

    2. Use Lookup Field Name (If Applicable):

       

      • Concept:

        • If the "xxx_subjectareaofinterest1id" field is a lookup to another entity (e.g., a custom entity), you might be able to use the lookup field's name instead of the GUID. 

      • Steps:

         

        • Try using the lookup field's name in your Handlebars code.

        • Example:

          {{#if (eq contact.xxx_subjectareaofinterest1id.name 'Acting and Drama')}}
          ----content----
          {{else if (eq contact.xxx_subjectareaofinterest1id.name 'Criminology')}}
          ----content----
          {{/if}}


      • Advantages:

        • More user-friendly than GUIDs. 

      • Disadvantages:

        • Might not work in all cases.
        • Depends on the lookup field's configuration. 

          •  

    3. Simplify Handlebars Expressions:

      • Concept:

        • Try simplifying your Handlebars expressions by breaking them down into smaller parts.
        • Use helper functions or variables to store intermediate results. 

      • Steps:

        • Experiment with different ways of writing your Handlebars code.
        • Try using helper functions or variables to simplify complex comparisons. 

      • Advantages:

        • Might improve compatibility with RTM. 

      • Disadvantages:

        • Can make the code more verbose.

          •  
         

    4. Contact Microsoft Support:

      • Concept:

        • If you've tried all other solutions and are still encountering errors, contact Microsoft Support.
        • Provide them with detailed information about your Handlebars code and the error messages you're getting. 

      • Advantages:

        • Microsoft Support might be able to provide specific guidance or identify a bug in RTM. 

      • Disadvantages:

        • Can be time-consuming.

          •  
          

      5.  

    Key Recommendations:

    • Use GUID comparison (Option 1) is the most reliable and recommended approach.
    • Try using the lookup field name (Option 2) if applicable.
    • Simplify your Handlebars expressions (Option 3) if necessary.
    • Contact Microsoft Support (Option 4) as a last resort.

      •  

    By using GUID comparison or simplifying your Handlebars expressions, you should be able to make your custom code work in RTM. Remember to test thoroughly and consider the user experience.

     
    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

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

🚀 Season of Sharing Community Challenge Launch!
Ask A Community Pro
Introducing our New Video Series: Community Spotlight

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Hamza H Profile Picture

Hamza H 142 Super User 2026 Season 1

#2
Nagaraju_Matta Profile Picture

Nagaraju_Matta 128

#3
11manish Profile Picture

11manish 119

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans