Announcements
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.
OData.Community.Display.V1.FormattedValue
Here are a few suggestions:
FormattedValue
equals()
equals(triggerOutputs()?['body']?['msp_pluginrtype@OData.Community.Display.V1.FormattedValue'], 'ExpectedValue')
outputs('Get_Plugin_Record')
Compose
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.
The main issue here is that OData.Community.Display.V1.FormattedValue is a property of the Dataverse record, not an array. Therefore, you don't need Filter array just to get the formatted value.Since your value is coming directly from the trigger, you can reference it directly in Compose: triggerOutputs()?['body/msp_plugintype@OData.Community.Display.V1.FormattedValue'] Or, if you are specifically using the Get Plugin Record action shown in your screenshot: outputs('Get_Plugin_Record')?['body/msp_plugintype@OData.Community.Display.V1.FormattedValue'] The important part is to use the correct action that actually contains the Dataverse record. Similar examples use triggerOutputs() for trigger data and outputs('Get_a_row_by_ID') for a Dataverse Get Row action.You don't need Filter array unless you are working with multiple records. Filter array expects an array as its input, which is why you're getting the error when passing the individual formatted-value property.I would also suggest adding a temporary Compose immediately after the Dataverse action and using: outputs('Get_Plugin_Record')?['body/msp_plugintype@OData.Community.Display.V1.FormattedValue'] Run the flow and check the Compose output. If it returns something like: Custom API then you can directly insert that Compose output into your email.If you're building the email body with HTML, you can also use: <p><strong>Plugin Type:</strong> @{outputs('Get_Plugin_Record')?['body/msp_plugintype@OData.Community.Display.V1.FormattedValue']}</p> One more thing: make sure msp_plugintype is actually populated. The FormattedValue annotation won't give you a useful value if the underlying field is null.So in your case, I'd remove the Filter array completely and reference the formatted-value property directly from the action/trigger that returned the Dataverse record. This should solve the issue.
The main issue here is that OData.Community.Display.V1.FormattedValue is a property of the Dataverse record, not an array. Therefore, you don't need Filter array just to get the formatted value.
Filter array
Since your value is coming directly from the trigger, you can reference it directly in Compose:
triggerOutputs()?['body/msp_plugintype@OData.Community.Display.V1.FormattedValue']
Or, if you are specifically using the Get Plugin Record action shown in your screenshot:
outputs('Get_Plugin_Record')?['body/msp_plugintype@OData.Community.Display.V1.FormattedValue']
The important part is to use the correct action that actually contains the Dataverse record. Similar examples use triggerOutputs() for trigger data and outputs('Get_a_row_by_ID') for a Dataverse Get Row action.
triggerOutputs()
outputs('Get_a_row_by_ID')
You don't need Filter array unless you are working with multiple records. Filter array expects an array as its input, which is why you're getting the error when passing the individual formatted-value property.
I would also suggest adding a temporary Compose immediately after the Dataverse action and using:
Run the flow and check the Compose output. If it returns something like:
Custom API
then you can directly insert that Compose output into your email.
If you're building the email body with HTML, you can also use:
<p><strong>Plugin Type:</strong> @{outputs('Get_Plugin_Record')?['body/msp_plugintype@OData.Community.Display.V1.FormattedValue']}</p>
One more thing: make sure msp_plugintype is actually populated. The FormattedValue annotation won't give you a useful value if the underlying field is null.
msp_plugintype
So in your case, I'd remove the Filter array completely and reference the formatted-value property directly from the action/trigger that returned the Dataverse record. This should solve the issue.
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.
Congratulations to our community stars!
Expanding mentorship, skilling, and AI innovation
These are the community rock stars!
Stay up to date on forum activity by subscribing.
11manish 82 Super User 2026 Season 2
André Arnaud de Cal... 44 Super User 2026 Season 2
ParthPatel249 40
