The ODataUnrecognizedPathException in your Power Automate flow, when creating a Product Price Level, occurs because the Dataverse Web API expects a specific syntax for referencing lookup fields.
When setting lookup fields in the "Add a new row" action for Product Price Levels (productpricelevel), use the plural schema name of the related table, followed by the GUID in parentheses.
Correct Field Formats:
- For the
Product field (lookup):
products(Product ID from the trigger)
- Example in Power Automate:
products(@{triggerOutputs()?['body/productid']})
- For the
Price List field (lookup):
pricelevels(hardcoded GUID of the Default Price List)
- Example in Power Automate:
pricelevels(YOUR_DEFAULT_PRICE_LIST_GUID_HERE)
Example of how your Power Automate "Add a new row" action fields should appear:
Product field: Type products( then insert the Dynamic content for the Product ID, then type ).
Price List field: Type pricelevels( then paste your hardcoded Price List GUID, then type ).
Additional Considerations:
Ensure you also define other required fields for Product Price Level to avoid further validation issues, such as:
Pricing Method: Set this (e.g., "Amount" if specifying a direct value).
Amount: (You're already setting this to 0.00).
By correcting the lookup field syntax to use the plural schema names (products and pricelevels), your ODataUnrecognizedPathException should be resolved.
✅ Mark this answer as verified if it helps you.
