An undeclared property 'alternis_calloutcome' which only has property annotations in the payload but no property value was found in the payload. In OData, only declared navigation properties and declared named streams can be represented as properties with

Question

An undeclared property 'alternis_calloutcome' which only has property annotations in the payload but no property value was found in the payload. In OData, only declared navigation properties and declared named streams can be represented as properties with

Nikita Randive 65

I am trying to add lookup fields in Dynamic CRM sink using mapping data flow in a pipeline. Getting the below error.

Job failed due to reason: Error response from server: Some({"error":{"code":"0x80048d19","message":"Error identified in Payload provided by the user for Entity :'phonecalls', For more information on this error please follow this help link https://go.microsoft.com/fwlink/?linkid=2195293 ----> InnerException : Microsoft.OData.ODataException: An undeclared property 'alternis_calloutcome' which only has property annotations in the payload but no property value was found in the payload. In OData, only declared navigation properties and declared named streams can be represented as properties without values.\r\n at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.ReadUndeclaredProperty(IODataJsonLightReaderResourceState resourceState, String propertyName, Boolean propertyWithValue)\r\n at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.ReadPropertyWithoutValue(IODataJsonLightReaderResourceState resourceState, String propertyName)\r\n at Microsoft.OData.JsonLight.ODataJsonLightResourc

KranthiPakala-MSFT 46,737 Reputation points Microsoft Employee Moderator

2023-05-12T23:03:40.7766667+00:00

@Nikita Randive Just checking in to see if the below information was helpful. If it answers your query, please do click Accept Answer and Yes for "was this answer helpful", as it might be beneficial to other community members reading this thread. If you have any further query, do let us know.

Thank you
KranthiPakala-MSFT 46,737 Reputation points Microsoft Employee Moderator

2023-05-17T22:15:32.28+00:00

@Nikita Randive We still have not heard back from you. Just wanted to check if the below information was helpful? If it answers your query, please do click Accept Answer and Yes for "was this answer helpful", as it might be beneficial to other community members reading this thread. And, if you have any further query do let us know.

Thank you

2 answers

Your answer

KranthiPakala-MSFT 46,737 Reputation points Microsoft Employee Moderator

2023-05-12T23:03:40.7766667+00:00

@Nikita Randive Just checking in to see if the below information was helpful. If it answers your query, please do click Accept Answer and Yes for "was this answer helpful", as it might be beneficial to other community members reading this thread. If you have any further query, do let us know.

Thank you
KranthiPakala-MSFT 46,737 Reputation points Microsoft Employee Moderator

2023-05-17T22:15:32.28+00:00

@Nikita Randive We still have not heard back from you. Just wanted to check if the below information was helpful? If it answers your query, please do click Accept Answer and Yes for "was this answer helpful", as it might be beneficial to other community members reading this thread. And, if you have any further query do let us know.

Thank you

Answer 1

KranthiPakala-MSFT 46,737 Microsoft Employee Moderator

Hi @Nikita Randive Thanks for using Microsoft Q&A forum and posting your query.

Looking at the error message it seems like the error is thrown by Dynamics CRM and nothing to do with Mapping data flow.

I'm not an expert with Dataverse (Dynamics CRM), but as per my research, but as per my research, the issue occurs if there is no/incorrect single-valued navigation property in the entity type. For more information about this error and possible solutions, please refer to this troubleshooting guide.

Troubleshooting Guide: Error identified in Payload provided by the user for Entity '{entity name}'

User's image

Here is a another Q&A thread where a similar issue has been discussed: Need single-valued navigation properties in OData for lookups

Related article: How to fix getting “Undeclared Property Error” when using Lookups with Dynamics 365 Web API

Hope this helps. And if you have further questions regarding this Dynamics CRM error, I recommend reaching out in Dynamics CRM community forum.

Please don’t forget to Accept Answer and Yes for "was this answer helpful" wherever the information provided helps you, this can be beneficial to other community members.

Nikita Randive 65 Reputation points

2023-05-24T07:57:11.4766667+00:00

Hi Kranthi,

Thanks for your reply. I will go through the link given. And will post the question on the Dynamics CRM community forum.
KranthiPakala-MSFT 46,737 Reputation points Microsoft Employee Moderator

2023-05-25T14:18:51.57+00:00

@Nikita Randive Thank you for the update!

Adding Dynamics community forum thread for others reference: https://community.dynamics.com/crm/f/microsoft-dynamics-crm-forum/488112/error-while-loading-data-to-lookup-fields-in-dynamics-crm-using-adf-mapping-dataflow/1343804

Please don’t forget to Accept Answer and Yes for "was this answer helpful" wherever the information provided helps you, this can be beneficial to other community members.
Nikita Randive 65 Reputation points

2023-05-26T06:48:49.6133333+00:00

Hi Kranthi,

Thanks for your help. I will post the answer once I get the solution for the same.

Answer 2

Sophia Grant 0

That’s an interesting observation about undeclared properties in OData. It’s essential to ensure that all navigation properties are properly declared to avoid payload inconsistencies. I recently explored some data mapping cases on Lee County Details that discussed similar structural validation issues, and it really helped clarify how these errors can be mitigated. Paying attention to proper schema definition can save a lot of debugging time later on.

Share via

An undeclared property 'alternis_calloutcome' which only has property annotations in the payload but no property value was found in the payload. In OData, only declared navigation properties and declared named streams can be represented as properties with

2 answers

Your answer