Running into the dreaded ODataUnrecognizedPathException in Power Automate? You’re not alone. This error often pops up when working with Dataverse lookups or custom tables, and the message “URL was not parsed” doesn’t exactly point you in the right direction. In this post, I’ll explain what causes the issue and how to fix it, so you can get your flow running again without hours of trial and error.
The root cause of this error is usually a lookup field that isn’t parsed correctly in Power Automate. The syntax for referencing lookups in Dataverse can be tricky, especially since it differs between out-of-the-box (OOTB) entities and custom entities. The correct format you need to use is always table set name(guid). In this post, I’ll walk through both cases and show you how to apply this syntax correctly so you can avoid the ODataUnrecognizedPathException altogether.
So to start we want to copy the set name of the table.
These entities are slightly easier in that their plural is usually +s. For example accounts, contacts, organisations, … Paste the set name with the GUID between brackets.
With these tables it is a bit more complicated, as you do not always know what the plural was when created. It can always be changed in the properties of the table: 
Copy the set name and perform the action as shown below.
Extra check
To be really sure which name to enter in your flow, you can go to the following URL and look for the (set) name:
https://[ORG].crm4.dynamics.com/api/data/v9.1
