Dynamics Community Forum Thread Details

Hi,

I'm creating an flow that can be manually triggered on an Quote. This flow should create a flow for the Account Manager of that specific Quote (so not for the person that triggers the flow) if the Quote is above the value of 5k.

I managed to have the task created when the flow is triggered but running into the problem when trying to link the Account Manager as the Owner of the Task. Getting the following error: Action 'Add_a_new_row' failed: URL was not parsed due to an ODataUnrecognizedPathException. Resource not found for the segment provided in the URL.

The same error comes back when trying to set the "Regarding" field within this task linking it to the Quote the flow was triggered from.

This is what the flow currently looks like:

The error 100% is with pulling in the Account Manager from the Quote but i can't seem to figure out how to solve this problem.

What am i missing?

Categories:

Microsoft Dynamics CRM

Dynamics 365 Sales

Hello LabTeoV,

You are likely encountering this error because you are trying to directly use a lookup field (like the Account Manager lookup on the Quote) in the "Owner (Value)" and "Regarding (Value)" fields of the "Create a new row" action for the Task without properly referencing the target entity and its ID.

Here's a breakdown of why this is happening and how to fix it:

Understanding Lookup Fields in Dataverse and Power Automate:

Lookup Fields: In Dataverse (formerly Common Data Service), a lookup field doesn't directly contain the user or record data. Instead, it holds a reference to another record. This reference typically includes:
- ID (GUID): The unique identifier of the related record.
- Logical Name of the Target Entity: The type of record the lookup points to (e.g., systemusers for a user, quote for a quote).
- Name (Optional): A display name for the linked record.

Power Automate "Create a new row" Action: When setting a lookup field in Power Automate's "Create a new row" action, you need to provide an array containing the ID of the target record, prefixed with the logical name of the target entity in parentheses.

How to Fix the "Owner (Value)" Field (Account Manager):

Identify the Schema Name of the Account Manager Lookup Field on the Quote Entity: In your Dataverse environment, find the Quote entity and identify the exact schema name of the lookup field that points to the Account Manager (it might be something like new_accountmanagerid or ownerid if the Account Manager is the Quote's owner).

Access the Account Manager's User ID: In your Power Automate flow, after the "When a record is selected" trigger and the "Get a row by ID" action for the Quote, you need to access the ID of the linked Account Manager. Assuming the schema name of your Account Manager lookup field is new_accountmanagerid, you can access the Account Manager's record using the following expression in the "Owner (Value)" field:
@{outputs('Get_a_row_by_ID')?['body/new_accountmanagerid']}

Important: This will give you the entire lookup object, which contains the ID, logical name, and potentially the name. You need to extract the ID. The correct format for the "Owner (Value)" field requires an array with the target entity logical name and the ID. Assuming the Account Manager is a system user, the correct expression would be:
[
"@odata.id=_x002f_systemusers(@{outputs('Get_a_row_by_ID')?['body/new_accountmanagerid']?['systemuserid']})"
]
Explanation:
- outputs('Get_a_row_by_ID')?['body/new_accountmanagerid']: This gets the value of the Account Manager lookup field from the Quote record.
- ?['systemuserid']: This extracts the systemuserid (the ID of the user record) from the lookup object. Make sure the lookup field on your Quote points to the systemusers entity. If it points to a Team, you'll need to use the Team ID and the logical name teams.
- "@odata.id=_x002f_systemusers(@{...})": This constructs the required format for a lookup value, specifying the target entity (systemusers) and the ID.

How to Fix the "Regarding (Value)" Field (Linking to the Quote):

You are trying to link the Task back to the Quote that triggered the flow. You need to provide the Quote's ID and the logical name of the Quote entity (quote).

Access the Quote's ID: The Quote's ID is available from the trigger (@{triggerOutputs()?['body/quoteid']}) or the "Get a row by ID" action (@{outputs('Get_a_row_by_ID')?['body/quoteid']}).

Format the "Regarding (Value)" Field: Use the following expression in the "Regarding (Value)" field of the "Create a new row" action for the Task:
[
"@odata.id=_x002f_quotes(@{triggerOutputs()?['body/quoteid']})"
]

Explanation:
- @{triggerOutputs()?['body/quoteid']}: This gets the ID of the Quote that triggered the flow.
- "@odata.id=_x002f_quotes(@{...})": This constructs the required format for a lookup value, specifying the target entity (quotes) and the ID.

Updated "Create a new row" Action for Task:

Your "Create a new row" action for the Task should look something like this (adjusting the schema name for the Account Manager lookup if needed):

Table name: Tasks
Subject: Follow up on Quote
Description: Follow up on selected quote, filling in any missing information fields and possibly closing the quote.
Due Date: @{utcNow()} (or your desired due date calculation)
Duration: 1 day(s)
Owner (Value):
[
"@odata.id=_x002f_systemusers(@{outputs('Get_a_row_by_ID')?['body/new_accountmanagerid']?['systemuserid']})"
]
(Replace new_accountmanagerid with the actual schema name of your Account Manager lookup field on the Quote.)

Priority: Select the priority.
Regarding (Value):
[

"@odata.id=_x002f_quotes(@{triggerOutputs()?['body/quoteid']})"

]

Important Considerations:

Schema Names: Ensure you are using the correct schema names for your fields (Account Manager lookup on Quote, Sales Stage, etc.). You can find these in the Power Apps solution explorer.
Account Manager Lookup Entity: Verify that the Account Manager lookup field on your Quote entity points to the systemusers entity (User). If it points to the teams entity, you'll need to adjust the "@odata.id" accordingly.
Error Handling: Consider adding error handling (e.g., using "Try-Catch") around the "Create a new row" action to gracefully handle cases where the Account Manager lookup might be empty on the Quote.

By correctly formatting the "Owner (Value)" and "Regarding (Value)" fields using the @odata.id syntax with the target entity's logical name and ID, you should be able to resolve the "ODataUnrecognizedPathException" and successfully link the Task to the Account Manager and the originating Quote. Remember to save and test your updated flow.

If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more. If you have further questions, please feel free to contact me.

My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics 365 query.

Regards,

Daivat Vartak

Community site session details

PowerAutomate flow creating Task

Helpful resources

News and Announcements

Quick Links

Responsible AI policies

Abhilash Warrier – Community Spotlight

Congratulations to the August Top 10 Community Leaders!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates