Updating field on update of another field using MS Flow

(0) Share

Report

Posted on by Andrew Stone

Hi,

I have a simple text field 'Productitemtextrollup' on OpptyProduct which is populated using Power Automate whenever an Opportunity Product record is created and a lookup field "Product" is populated (this field looks up the Product table). This flow Gets the txt label and puts it in the simple txt field.

I would now like to create another flow which updates this text field if there are any changes to the Product Lookup field after the initial create, for example if a sales person changes the product.

I believe that you cannot do this via a D365 trigger (creates an infinite loop), but can achieve this via using the Common Data Service.

My question is how I can structure the flow in Power Automate?

So far, I have set a trigger based on Common Data Service ("When a record is updated") then used GET Record and UPDATE a record to write the text label of the product into the simple text field 'Productitemtextrollup', but it does not appear to be working. The CDS solution appears to require a 'status' field on an entity to be used as a filter, so the update doesnt create an infinite loop.

If it helps, the 'Productitemtxtrollup is being used as afilter in a rollup field (a workaround as Lookups cannot be used).

Thanks

I have the same question (0)

All responses (6)

Answers (1)

Verified answer

ba365guy 2,950 on at

Like (0)

Report

I tried below, it is working.

Was this reply helpful? Yes No
Suggested answer

Inogic 682 on at

Like (2)

Report

Hi Andrew,

You should not be using the D365 connector any more. Common Data Service is the connector to use for all flow operations for D365 apps. Common Data Service itself has 2 variants Common Data Service and Common Data Service (Current) as can be shown in the picture below

The Common Data Service (Current) connector will show up only when you try to create a flow from within a solution from https://web.powerapps.com. choose your solution and then New --> Flow

The CDS (Current) connector has the highlighted trigger When a record is created/updated/deleted. Use that to make sure the flow that you design can be triggered both on Create and Update. Set the filter attributes to ensure that the flow is triggered only when the Opp Product is modified.

HTH

~roohi

Was this reply helpful? Yes No
Andrew Stone 22 on at

Like (1)

Report

Thanks very much for your help ba365guy, much appreciated. I've rebuilt the original flow using Common Data Service below (per Roohi's post) and that is working too now.

Was this reply helpful? Yes No
ba365guy 2,950 on at

Like (1)

Report

Yeah... Going forward use CDS (only)

Was this reply helpful? Yes No
Inogic 682 on at

Like (1)

Report

Hi Andrew,

Glad it helped. But a critical point to note is that wherever possible you should use CDS (Current) as it avoids the complexity of having to set the environment in the flow when you move the flow from Dev - TEST - Prod.

The CDS (Current) connector by default connects to the current environment from which the connector is being accessed/triggered. The CDS (Current) is the connector where all new advancements would show up too.

Thanks!

~roohi

Was this reply helpful? Yes No
Andrew Stone 22 on at

Like (0)

Report

Thanks - so ive built everything on our Sandbox environment so far - is 'current' in your post referring to 'current' in the drop down when I create a new flow?

In otherwords, if I log in to the PROD envionment, I shoud select 'CURRENT' not the name of my PROD environment?

Thanks,

Andrew

Was this reply helpful? Yes No