Hello User,
The error you're encountering, ODataUnrecognizedPathException, typically occurs when the path used in the Dataverse API call is incorrect or incomplete, often due to missing or incorrect segments in the URL. Since you’ve successfully resolved this for sales opportunities, it’s likely related to required fields for the Quote entity, or a reference to a related table that isn't properly set.
For creating a Quote in Dataverse (via Power Automate), here are some key points and fields that might help you resolve this issue:
Key Required Fields:
1. name: The name or title of the quote (required).
2. customerid: This is the lookup for the customer related to the quote. It could be an account or a contact.
3. transactioncurrencyid: The currency for the quote.
4. pricelevelid: The price list associated with the quote.
5. quote number: It is auto-generated, but you can check if your instance requires this to be set manually (in some customized instances).
6. potentialcustomerid: This may refer to the account or contact that the quote is associated with.
7. opportunityid: If the quote is related to a sales opportunity, this is the lookup to that opportunity.
Revisionnumber:
If you are unable to see the revisionnumber, this may be because it's automatically generated by the system and doesn't need to be explicitly set when creating the quote. Some fields are auto-managed by Dataverse.
Debugging Steps:
1. Use Postman/Fiddler: If you're comfortable using tools like Postman or Fiddler, you can make a direct API call to the Dataverse and get more details on the fields required.
2. Schema Check: In the Dataverse admin interface, check the schema for the "Quote" entity to see any other required fields or relationships that you may have missed.
3. Field Validation: Double-check if any business rules or plugins are enforcing required fields that are not marked as such on the table.
If this doesn't help resolve the issue, I suggest adding more detailed logging in Power Automate to capture the exact payload and path being used, which can help in identifying the specific field or URL causing the error.
Thank you,
Amit Katariya