Microsoft Dynamics 365 | Integration, Dataverse...

How to create a workflow to run 45 days from Estimated Start Date field?

(0) Share

Report

Posted on by USA80

Hello,

How and what is the best way to create a workflow to send an email when the difference between the Estimated Start Date field and now is 45 days? I created a calculated field to show the difference between estimated start date and now. Then I created another field to copy that value into another field as I can't use a calculated field in a wait condition. How can I get this to work, I am sure there is a easier/better way.

I have something like this, but it just stays in a waiting status

Thank you in advance.

I have the same question (0)

All responses (8)

Answers (0)

AriaConsulting 2 on at

Like (0)

Report

Hi USA80, first question is which D365 app is this for? Sales or Marketing App? If this is for the Marketing app you can create that easily in the Journey design canvas.

Was this reply helpful? Yes No
USA80 26 on at

Like (0)

Report

This is just a custom app (not a marketing app).

Was this reply helpful? Yes No
AriaConsulting 2 on at

Like (0)

Report

In that case, I would suggest using Power Automate.

Was this reply helpful? Yes No
USA80 26 on at

Like (0)

Report

Would it be possible for you to show me the steps for what I am asking for?

Was this reply helpful? Yes No
Suggested answer

AriaConsulting 2 on at

Like (0)

Report

Well that starts to get into free consulting . However, the basics are:

-go to flow.microsoft.com, choose your environment (start with sandbox)

-Choose the type of Flow you want (I assume you want an automated scenario so that would be a cloud flow)

-As I assume your table/entity is in Dataverse you can start with the Dataverse 'when a row is added, modified, or deleted

-Choose your values for Change type, Table name, and Scope and then any filters to make sure it only runs when req'd

-Add a Condition action for your yes and no paths logic and for the yes path add a Date Time Action (there's 6 to choose from)

-Once the Date Time is satisfied (45 days in your case) then add an Office 365 Mail action (there's like 30+ options in the list)

-While not required, it's not a bad idea to add terminate actions for your condition branches.

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

Hi USA80,

From your screenshot, you have set a wait condition for copied field.

A wait condition tells the workflow to wait until some specific action has occurred, such as a field changing or updating to a specific value.

But the workflow just stays in a waiting status, can you answer following questions:

(1) Have you checked the value of the calculated field and copied field?

(2) Copied field’s value is whether it is equal to the value set in the workflow?

(3) What way you are using to copy calculated field value to another field?

Also, do you know the Timeout?

A Process Timeout tells the Workflow to wait for a specific amount of time or until a specific date. The former is essential for building workflows that should space out the execution of certain steps while remaining fully automated, while the latter is needed when a given step has to execute on a certain day or time. You can include a Process Timeout in a workflow by selecting Add Step > Wait Condition, and then adjusting the values as shown here:

It is very good but has a small flaw, the number of days cannot be set beyond 31, which makes it inapplicable to the current scenario

Regards,

Leah Ju

Please mark as verified if the answer is helpful. Welcome to join hot discussions in Dynamics 365 Forums.

Was this reply helpful? Yes No
AriaConsulting 2 on at

Like (0)

Report

Hence one of the reasons I suggested using Flow. Easier, more flexible, and I strongly believe MS will eventually deprecate those old CRM worklfows. No idea when, but pretty much guaranteed.

Was this reply helpful? Yes No
USA80 26 on at

Like (0)

Report

Still having issues, if someone could supply screen shots of the flow that would be great, thank you.

Was this reply helpful? Yes No