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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics 365 | Integration, Dataverse... / How to use OData.Commu...
Microsoft Dynamics 365 | Integration, Dataverse...
Suggested Answer

How to use OData.Community.Display.V1.FormattedValue triggerOutputs method in Compose Action

(4) ShareShare
ReportReport
Posted on by AC-20080811-0 Microsoft Employee
Hi Team,
 
I am trying to use an OData.Community.Display.V1.FormattedValue of a field in the compose section to create a mail for the team, like this, but it's not showing any value in the mail:

 
I have tried to use the filter query also, but I am getting errors as it wants the input to be an array. I am using an OpenApiConnection to get the data and msp_plugintype@OData.Community.Display.V1.FormattedValue is present at the body of the triggerOutputs. 

 

  Please guide me how can I use the OData.Community.Display.V1.FormattedValue in the compose field to generate the mail successfully.
 
Categories:
Power Platform integration
I have the same question (1)
  • Suggested answer
    DAnny3211 Profile Picture
    DAnny3211 11,417 Super User 2026 Season 1 on at

    Hi,

     

    Thanks for sharing the details. When using OData.Community.Display.V1.FormattedValue in a Power Automate flow to format values for email output, it's important to ensure that the syntax and data structure are correctly handled.

     

    Here are a few suggestions:

     

    • Check the data type: The FormattedValue is typically a string, but if you're using it in a filter or condition that expects an array, you’ll need to wrap it appropriately or adjust the logic to compare strings.

    • Use expressions carefully: In your equals() condition, make sure the path to the value is correct. You might try: 
      equals(triggerOutputs()?['body']?['msp_pluginrtype@OData.Community.Display.V1.FormattedValue'], 'ExpectedValue')

      or use outputs('Get_Plugin_Record') if referencing a previous step.

    • Debug with Compose: Add a Compose action to output the full body of the trigger or the plugin record step. This will help confirm the exact structure and whether the formatted value is present.

    • Ensure the field is populated: Sometimes the formatted value won’t appear if the original field is null or not properly retrieved.


      •  
     

    Please verify if this response was helpful.

     

    Thanks and best regards,\
    Daniele\
    Note: This response was prepared with support from Copilot to ensure clarity and completeness.

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

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
11manish Profile Picture

11manish 174

#2
ManoVerse Profile Picture

ManoVerse 58 Super User 2026 Season 1

#3
Niki Patel Profile Picture

Niki Patel 42

Last 30 days Overall leaderboard

Featured topics

Welcome to the Microsoft Dynamics 365 forum!
Identifying an Org as CDS or Dynamics
Get batch job history log from D365 FO to Power Automate
Gross and Net Weight of Shipments feeding back into Sales Order (from External Source)

Product updates

Dynamics 365 release plans