Showing results for 
Search instead for 
Did you mean: 

Dynamics 365 - Header - Include OData Annotations

The Dynamics 365 Get Record operation doesn't seem to have the capability to specify "odata.include-annotations" in the header. This is normally set to odata.include-annotations="*". For datatypes like EntityReference and OptionSet, not including this header means that the underlying text behind the Guid or Integer cannot be seen, as there is no formatted value on the response.


With odata.include-annotations header

	@odata.context: "$metadata#accounts(_modifiedby_value)",
	@Microsoft.Dynamics.CRM.totalrecordcount: -1,
	@Microsoft.Dynamics.CRM.totalrecordcountlimitexceeded: false,
	value: [0: {
		@odata.etag: "W/"4106932"",
		_modifiedby_value@OData.Community.Display.V1.FormattedValue: "Max Power",
		_modifiedby_value@Microsoft.Dynamics.CRM.lookuplogicalname: "systemuser",
		_modifiedby_value: "edf0b0bf-8949-4f09-9d5e-a41b8c31de00",
		accountid: "55ee1933-35ad-e711-a842-000d3ad0ed15"

Without odata.include-annotations header

	"@odata.context": "$metadata#accounts(_modifiedby_value)",
	"value": [{
		"@odata.etag": "W/\"4106932\"",
		"_modifiedby_value": "edf0b0bf-8949-4f09-9d5e-a41b8c31de00",
		"accountid": "55ee1933-35ad-e711-a842-000d3ad0ed15"
Status: New
Frequent Visitor

@rajyraman  -  Don't we have solution for this yet ?

New Member

@Praveenpk365 you can use the HTTP with Azure AD connector's Invoke an HTTP request action to retrieve formatted values as a work around for now.

Frequent Visitor

I can't believe it is this difficult to get/use the label value of a select list (as text) within a flow!!


This was BASIC in workflows...


@benitezhere - I love your demo's online - do you have anything easier for this?




Mark Fletcher

Kudo Kingpin


With the latest update of Common Data Service (current environment) connector, we can now query the formatted values of supported field types such as lookup display name, option set value label, formatted date/time by using the OData.Community.Display.V1.FormattedValue property of the field in the expression.


@LinnZawWin- Good one Linn. So, it looks like they are in the process of fixing this.