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.

Hello,

 

For the purpose of integrating Meta Leads to DYnamics 365, I am trying to map a Source Campaign from Dynamics 365 - however I am having the following error:

The app returned "URL was not parsed due to an ODataUnrecognizedPathException. Resource not found for the segment provided in the URL.".

 

You will see below I have searched for the source campaign with a dedicated step, and retrieving it dynamically in the last step, but it seems it is not working.

 

The full troubleshooting message from Zapier AI:

 

The error message "URL was not parsed due to an ODataUnrecognizedPathException. Resource not found for the segment provided in the URL." typically indicates that the URL used in the API call is incorrect or that the resource path specified does not exist in the Microsoft Dynamics 365 CRM environment. This can happen if the entity name or the field names in the URL are misspelled or if the entity does not exist in the CRM system. In your case, it seems like the leadCreate action is trying to access a resource that is not correctly defined in the URL.

To resolve this issue, first, ensure that the entity name and field names used in the Zap are correctly spelled and match those in your Dynamics 365 CRM setup. Check the configuration of the "leadCreate" action to ensure that the correct entity and fields are being targeted. Additionally, verify that the campaignid being used is valid and exists in your CRM system. You can use the output from the previous step to confirm that the campaignid is correctly passed and matches an existing campaign. If the issue persists, consider using a "Find Record" action before the "leadCreate" step to ensure that the necessary data is correctly retrieved and available for the subsequent steps.

 

My setup:

 

Hi ​@Zappito 

For us to have more info about the error, post screenshots showing how your Zap steps are configured in EDIT mode with the field mappings visible.

Hi ​@Troy Tessalone 

Thanks for the advice. Below steps - I am only including the relevant fields for the mapping, the others are just names/last names etc.

1.

 

 

2.

 

​@Zappito 

What about the other fields not shown in Zap step 3? (scrollbar is at the bottom)

Try changing the Filter by to “Required”.

 

Help links for using MS Dynamics 365 in Zaps: https://zapier.com/apps/microsoft-dynamics-crm/integrations#help

 

TIP: Click on field labels that are underlined to see a tooltip with more info that may provide guidance.

 

 

​@Troy Tessalone Here are the required fields step 3:

 

​@Zappito 

Click the field labels to see tooltips with more info about the field that may provide guidance about expected values and formats.

 

Things to check/try:

  • Try testing with a valid last name instead of a long text string that includes “test” and “:”
  • For Country/Region, may expect the abbreviation instead of the full name
  • For Topic, may expect specific values or have a max character length
  • Check any fields that you have values populated whether static or dynamic

 

 

Hi there, ​@Zappito 👋

How did you get on with Troy’s suggestions here—did they help to get things sorted?

Want to make sure you’re all set, so let us know if you’re still stuck at all! 

Terms & Conditions