Dynamics Community Forum Thread Details

Hello KR-10100945-0,

You've correctly identified the likely root cause: the field locationname (from the related location entity) is not directly available on the Participation entity from which your email is being sent. The fact that Level-up shows the formatted value in _location_value@OData.Community.Display.V1.FormattedValue confirms this.

Here's a breakdown of why this happens and how to solve it within your Power Automate flow and Dynamics 365 email template:

Understanding the Data Structure:

Your email template is likely associated with the Participation entity.

The location information is stored in a separate entity (let's assume it's called Location).

There's a relationship (likely a lookup field on the Participation entity) that links a Participation record to a specific Location record. This lookup field will have a schema name like _location_value.

When you use {!location:locationname;} in your email template, Dynamics 365 tries to directly access a field named locationname on the Participation entity, which doesn't exist.

Solution: Accessing Related Entity Attributes in Power Automate

You need to explicitly retrieve the related Location record within your Power Automate flow to access its locationname attribute. Here's how you can modify your flow:

Trigger: Your existing trigger (likely based on some condition related to the summer school participation) is fine.

Get the Participation Record: You probably already have an action to retrieve the Participation record that triggers the email. Ensure this action includes the lookup field to the Location entity (e.g., _location_value).

Add a "Get record" Action for the Related Location:
- After you retrieve the Participation record, add a new action: "Get record".
- Environment: Select your Dynamics 365 environment.
- Entity name: Select your Location entity (the actual schema name of your Location entity).
- Record identifier: In this field, you need to provide the ID of the related Location record from the Participation record. You can get this using dynamic content from the previous "Get record" (Participation) action. Look for the _location_value output. This field contains the GUID of the linked Location record.

Use Dynamic Content from the "Get record (Location)" Action:
- Now, when you configure the action to "Send an email (using a Dynamics 365 email template)", you should have access to dynamic content not only from the Participation record but also from the "Get record (Location)" action you just added.
- Look for the locationname attribute within the dynamic content of the "Get record (Location)" action.

Modify the Email Template in Dynamics 365:
- Go to your Dynamics 365 email template.
- Instead of using {!location:locationname;}, you need to reference the locationname attribute from the related Location entity that you are now explicitly retrieving in your Power Automate flow.
- The exact syntax for referencing attributes from related entities within an email template populated by a Power Automate flow can vary slightly depending on how the flow passes the data.
Here are a couple of common approaches:
- If Power Automate directly populates the "Regarding" field of the email with the Participation record: In this case, the email template might not directly understand the relationship to the fetched Location record. You might need to pass the locationname as a separate dynamic property from your flow.
- Passing Data as Input Parameters to the Email Template (More Robust): A cleaner approach is to use the "Perform a bound action" or "Perform an unbound action" step in Power Automate to send the email using the SendEmailFromTemplate action. This allows you to pass a JSON object containing the Participation record and the retrieved Location record (including the locationname). You can then reference these parameters in your email template using a specific syntax (often involving the parameter name and the attribute).
  
  Example using "Perform a bound action" (assuming the email is related to the Participation record):
  - Action: "Perform a bound action"
  - Entity name: participations (your Participation entity schema name)
  - Record ID: The ID of the current Participation record.
  - Action name: Microsoft.Dynamics.CRM.SendEmailFromTemplate
  - Target: (Should be automatically populated with the Participation record)
  - TemplateId: The GUID of your email template.
  - Parameter Name (e.g., relatedData): Enter a name for your parameter.
  - Parameter Value (Expression):
    {
    "participation": @{outputs('Get_the_participation_record')},
    "location": @{outputs('Get_record_(Location)')}
    }
  - In your Email Template: You would then reference the location name using a syntax that accesses this relatedData parameter. The exact syntax depends on the Dynamics 365 version and how the template rendering engine handles custom parameters. It might look something like:
    {{relatedData.location.locationname}}
    
    or a similar dot-notation based access. You might need to experiment or consult Dynamics 365 documentation for the precise syntax for accessing custom parameters in email templates.

Using the Formatted Value (Less Ideal for Direct Use):

While you see the formatted value in _location_value@OData.Community.Display.V1.FormattedValue, this is primarily for display purposes and might not be directly usable as a value in your email content. It's a string representation of the lookup value (likely the name of the location). The more reliable way is to fetch the actual Location record and use its attributes.

In summary, the solution involves:

Retrieving the related Location record in your Power Automate flow.

Passing the locationname attribute from the retrieved Location record to your email template (either implicitly if the template context allows or explicitly as a parameter).

Adjusting the syntax in your email template to correctly reference the locationname from the related Location data.

The "Perform a bound action" with a custom parameter is generally the most robust and flexible way to pass related data to email templates in Power Automate. Remember to test your flow and email template thoroughly after making these changes.

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

Community site session details

Dynamics E-mail Template - Dynamic Content - Resolved but no value

Helpful resources

News and Announcements

Quick Links

Responsible AI policies

Mansi Soni – Community Spotlight

Congratulations to the July Top 10 Community Leaders!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates