Answered

URL was not parsed due to an ODataUnrecognizedPathException

(1) Share

Report

Posted on by jamest1994

105

I'm getting the following error when trying to add a row to dataverse containing a lookup column value. URL was not parsed due to an ODataUnrecognizedPathException. Resource not found for the segment provided in the URL.

I'm using a variable to set the value of the conversation value in the format of conversations(), and the flow runs successfully when this is removed, despite being set up in the exact same way as my contact variable shown below.

I checked the raw inputs of the failed step on the flow run and can see that these values are being passed through correctly and I can find that conversation ID in the table, yet contacts works but conversations fails. Any help would be appreciated as I'm lost with this one! Thanks

"item/cbs_Contact_cbs_CustomerFeedback@odata.bind": "contacts(9fd121f8-6a38-ef11-a316-6045bd115f3f)",
"item/cbs_Conversation_cbs_CustomerFeedback@odata.bind": "conversations(fd6b32ad-ac6d-497c-8e88-53bee5b30ce0)",

Categories:

Building flows

I have the same question (0)

All responses (2)

Answers (1)

Sort by

Verified answer

chiaraalina 2,489 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi jamest1994,

The error you’re encountering could be due to using an incorrect entity set name in your @odata.bind URL.

Please go to your Dataverse, open the table you want to reference, and identify the schema name.

Once you have the schema name, use it in plural form by adding an “s” at the end (unless it’s an irregular plural), and use that in your Power Automate flow instead of “conversations.”

Hope this helps!

Was this reply helpful? Yes No
jamest1994 105 on at

Like
a
(1)

Report
Copy link

Link copied!

Thank you very much, I've resubmitted the flow with your suggestion using plural schema name and that worked!

Was this reply helpful? Yes No