Create Schedule Cloud Flow

Writing a scheduled cloud flow is very convenient when we do not have to add any flow trigger and it runs at a scheduled time.

Here is a Scheduled Power Automate Cloud Flow which runs every day to check customer auto-debit date and sends mail to the customer the day before the auto-debit is scheduled.


Follow these steps to initiate the scheduled workflow:

1. Navigate to 'Power Apps.'

2. Click on 'Flows.'

3. Choose 'New flow.'

4. Opt for 'Scheduled Cloud Flow.'


You are now prompted to:

1. Provide a name for your cloud flow.

2. Choose the start date and time for the flow.

3. Specify the recurrence frequency, which can be set to every minute, hour, day, week, or month.

These settings allow you to tailor the scheduled workflow according to your specific requirements.



After initiating the scheduled workflow, proceed by clicking on "Next Step" and then select 'List Rows' from 'Microsoft Dataverse.'




The 'List Rows' action enables access to entity data. Make sure to specify the relevant entity by selecting it in the 'Table Name' field.



In the next step, choose 'Condition' under 'Actions' to evaluate specific conditions. In this case, verify if the auto-debit date for a customer is scheduled for the next day.
This formula ensures that you are comparing the current date with the date exactly one day in the future - formatDateTime(addDays(utcNow(),1),'yyyy-MM-dd')

 
Following the conditional check for the next day auto-debit date using the conditional branch, proceed by selecting 'Send an Email' under 'Actions' to send emails to all customers regarding their auto-debit.



This is a straightforward Scheduled Cloud Flow that executes without requiring a specific trigger event.




Comments

Post a Comment

Popular posts from this blog

Customizing Dynamics 365 with JavaScript

Image
 Microsoft Dynamics 365 (D365) is a great tool for managing business processes, but to make it work best for your organization, using JavaScript can be very helpful. JavaScript lets you add custom features that improve how users interact with the system and make tasks easier to complete. In this post, we'll look at some simple JavaScript code examples for D365 that can help you do things like show or hide fields, check user input, create alert messages, and automatically set field values. 1. Controlling Field Visibility           Dynamic forms improve the user experience by showing only the fields that are relevant based on the user’s input. For example, you can use JavaScript to control which fields are displayed depending on the user's selections. In the following example, we'll look at how to show or hide a field based on the country selected from an option set. If the user chooses "UK," an additional field will appear, allowing them to select citie...
Read more

Understanding Business Rules in D365

Image
Business rules are crucial in streamlining processes and automating tasks within Dynamics 365. They effortlessly handle things like setting default values for fields, adjusting one field based on another, toggling field visibility, and even locking or unlocking fields as needed. These rules work behind the scenes, making processes smoother and more efficient without requiring constant manual intervention.  Various components in Business rules are used to perform various tasks, below is an example of the “Set Field Value” component which is used to automatically set the Gender field value in a form based on the user-selected prefix; if the prefix is "Ms", “Miss” or "Mrs," set the Gender to Female; otherwise, set it to Male. Begin by navigating to the form where you want to implement the Business Rule. Click on the 'Business Rule' icon and click on the 'New Business Rule' button. After initiating the Business Rule, simply click the down arrow to enter ...
Read more

Difference between Background and Real-Time Workflows

Background Workflow Operates in the background, requiring users to refresh pages to see changes after saving records, however, this doesn't interrupt users' ability to continue their work. If a step fails in the background workflow, the process halts at the failure step, and changes made by previous steps are kept.  Errors do not appear as pop-ups; administrators must check system job logs to identify failed processes. Background workflows are designed to minimize resource usage, ensuring they do not disrupt system processing. Troubleshooting background workflows is straightforward as it's easy to monitor which process failed at which point. Real-Time Workflow Changes are instantly reflected upon saving a record, without requiring page refreshes. Users may need to wait briefly for the process to complete, but it's not typically noticeable. If a step fails in a real-time workflow, a pop-up error message notifies users of the failed process. Real-time workflows typically ...
Read more