Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

I am using a status column change on monday to create a Time card entry (Custom entity) in Dynamics 365. 

I can map and execute the Zap when it’s just the text fields in Dynamics that I am populating but as soon as I arrive at the “Lookup Fields” ie. Contacts, (in this case, it’s Advisors and Clients). I get the error below. I have been struggling to make it work but alway send up with this same error.   

 

Example is the Status column (or text column, Ive used both) says “John Smith”. All I want is for Zapier to create the timecard entry in Dynamics then assign the client and Advisor from the monday text fields. 

 

“Error identified in Payload provided by the user for Entity :'spk_timeentries', 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 'spk_Advisor' 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.” 

 

I feel like I’m going crazy! Can anyone help with this? 

 

Thanks.

Hi there ​@techadminspark,

Before we dig deeper into this, would you mind sharing a detailed screenshot of how your Zap is configured? Also, please share a screenshot of the action step that shows all of its fields in the “CONFIGURE” section.

Please don't include personal information in the screenshot, or be sure blur out any personal information.

Thanks!

 

ZAP overview
“Find Contact” step - I Didn’t have this originally but google results recommended setting it up like this. 

 

 

These are the steps for “Create Custom Entity” 

 

“Client” and “spk_Advisor” are both “lookup” fields in Dynamics. these are the ones that cause the error code below. 

Failed to create a custom entity in Microsoft Dynamics 365 CRM

The app returned "Error identified in Payload provided by the user for Entity :'spk_timeentries', For more information on this error please follow this help link https://go.microsoft.com/fwlink/?linkid=2195293 ----> ...". Error identified in Payload provided by the user for Entity :'spk_timeentries', 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 'spk_Advisor' 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.

 

 

Hi there ​@techadminspark,

Thanks for the screenshots!

I believe the error you’re running into is because of the “spk_Advisor” field there’s an invalid navigation property name is sent with a request. I’m not really familiar with Microsoft Dynamics 365 CRM. However, Microsoft provided instructions on how to avoid this error.

You can read them here: https://learn.microsoft.com/en-us/troubleshoot/power-platform/dataverse/dataverse-web-api-and-sdk/web-api-client-errors#innerexception--microsoftodataodataexception-an-undeclared-property--was-found-in-the-payload

Hopefully, this helps!

Terms & Conditions