Any idea on how to rewrite Async workflow to MS Flow/Power Automate?

(0) Share

Report

Posted on by Community Member

Hello,

I need to convert following to MS Flow/Power Automate or Sync WF. Classical Sync WF doesn't achieve what's it meant for. Any ideas?

Thanks in advance

Nikhil

I have the same question (0)

All responses (7)

Answers (1)

Suggested answer

Community Member on at

Like (0)

Report

RE: Any idea on how to rewrite Async workflow to MS Flow/Power Automate?

Hi Niku123,

You can convert Async workflow to Sync workflow through the 'Convert to a real-time workflow ' button:

"Classical Sync WF doesn't achieve what's it meant for."

What is the purpose of this workflow and can you provide a specific scenario?

And you can use 'Condition' and 'Update a row' actions to replace steps that showed in the screenshot.

Can you provide more details about the original workflow(trigger, other steps..)?

Was this reply helpful? Yes No
Suggested answer

Bipin D365 28,983 Moderator on at

Like (0)

Report

RE: Any idea on how to rewrite Async workflow to MS Flow/Power Automate?

Hi,

have you tried deactivating and converting it to Real time workflow by clicking on ribbon button?

Only wait & Timeout is not supported in Classic sync workflow. Apart from this it should be easy to convert to sync workflow.

Please provide the screenshot of whole workflow to replicate it into MS flow/power automate.

Please mark my answer verified if this is helpful!

Regards,

Bipin Kumar

Follow my Blog: xrmdynamicscrm.wordpress.com/

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: Any idea on how to rewrite Async workflow to MS Flow/Power Automate?

Thanks all for your replies however given the same, here it's a complete picture;

Following are my conditions used in WF

and here it's a complete WF

so basically ask here is I need to convert to real time WF which can be done on ribbon button click, I also know that however I want

"Lead and application should not be listed as connections of contact from qualified lead" which means both two connections created should be in inactive status. Right now, one record remains in active status while other goes in to inactive status.

Also, I need to know how we can reference in Power Automate - let's say for e.g. Connected To(Opportunity) from Connections entity when record is created. One might call them as related entity.

I hope it's clear now.

Thanks

Nikhil

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

RE: Any idea on how to rewrite Async workflow to MS Flow/Power Automate?

Hi Niku123,

1.how we can reference in Power Automate:

You can use 'Get a row by ID' action to get parent records based on of lookup fields.

Then you can get information of opportunity from the step:

2. both two connections created should be in inactive status:

When you create connections between contact and opportunity, two connections can be created automatically,They correspond to each other in the Connected from and Connected to fields, which means that the contact is 'Connected to' in one connection and 'Connected from' in another connection.

But conditions you provided limit the 'Connected from' field must be contact and 'Connected to' field must be opportunity/lead, so only one connection satisfy these conditions, another does not to the extent that it's status can't be change.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: Any idea on how to rewrite Async workflow to MS Flow/Power Automate?

Thanks Leah, your reply is much appreciated and v.much inline on what I wanted.

However for me, there is also Lead entity which needs to fit in power automate - may be parallel branch. As you know with both lead and opportunity(inclusive), there would be 4 connections created(overall) and they go in inactive status with the flow but the flow run itself keeps failing all four times with error as "Opportunity with id doesn't exist" and "Lead with id doesn't exist".

Any inputs?

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (0)

Report

RE: Any idea on how to rewrite Async workflow to MS Flow/Power Automate?

Hi Niku123,

As I mentioned above, the opportunity/lead exists on the two connection records in the "Connected to" and "Connected from" fields respectively.

In my original example, i only get the opportunity from "Connected to" field, so another connection that opportunity is "Connected from" will run failed.

so you need add condition to specify it's type before 'Get a row by ID' action:

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: Any idea on how to rewrite Async workflow to MS Flow/Power Automate?

Thank you so much. I got it working with below expression CRM.LookupLogicalName

Was this reply helpful? Yes No