Answered

Problem with referencing OData ID in flow

(0) Share

Report

Posted on by joe_speed

Hi,

I am trying to repair a flow that I had up and working only 2 weeks ago. The flow is designed to start an Approvals process when a row in our Dataverse is modified.

After the approval is run it should then write back that approval to the same row in the Dataverse. To do so I was using the Dynamic content "OData ID" from the trigger action. 2 weeks ago this was workings fine - but today when I try to run the same flow I instead get this error:

It seems like the Power Automate system can no longer pick p what the OData ID is from the trigger event.

Has anyone else encountered this issue, or does anyone have any possible work arounds?

Thank you!

Categories:

Building flows

I have the same question (0)

All responses (5)

Answers (1)

joe_speed 15 on at

Like (0)

Report
Copy link

Link copied!

Apologies - I think that it might actually be the case that the flow has never actually worked as intended.

However, I still need to know how I can dynamically specify the row to be modified in a Power Automate flow so that it modifies the same row that triggered the flow.

Was this reply helpful? Yes No
Verified answer

joe_speed 15 on at

Like (0)

Report
Copy link

Link copied!

OK, so I have actually managed to find the solution. The problem was in using the OData ID in the first place. I should have just been using the Dynamic Content that referred to the Items ID from it's home table.

Still need to work out where OData ID would be appropriate to use - but for my case it was not relevant.

Was this reply helpful? Yes No
Expiscornovus 33,768 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @joe_speed,

You could refer to the unique identifier, which probably is also called Requisition.

Btw, are you using any kind of checks before updating the row? When you triggering it when modified and you are also modifying the same row in your flow you could potentially run in to a continuous flow loop 😃

Was this reply helpful? Yes No
joe_speed 15 on at

Like (1)

Report
Copy link

Link copied!

Hi - thanks for your response.

You're exactly right - that is the correct unique identifier I should have been using - guess it took me taking the plunge and asking the question for my brain to finally catch up!

And thanks for the advice on checks on the row. The flow is set up so that the update is being applied to different fields than begin the trigger, and I have some local workflows in Dynamics 365 that fire before this flow that do some checking on the rows too.

Really appreciate the help!

Was this reply helpful? Yes No
HenriHaa 2 on at

Like (0)

Report
Copy link

Link copied!

What i´ve noticed that the trigger outputs doesnt provide the odata.id of the record which has the value URL + id of the record.

But If you get the record again with "Get a row by ID" you can get the Odata.ID on the outputs of that one. It is kinda inconvenient but doesnt really add noticable delay on the flow.

The Odata.ID is needed for example if you want to generate default tasks on a custom table and straight giving the tasks the relation to the custom table. For some reason it needs to be the Odata.ID.

Also one tip ive learned is to just first query everything on the record and then searching stuff on the output data. 🙂

Was this reply helpful? Yes No