Launching a Process in a Dynamics 365 Batch

In this case, we’re using a solution from Microsoft Labs. This section describes how to execute Dynamics 365 workflows in batch processing at a specified time.

Important note: If you wish to use the Change Tracking Solution in your own environment, please do so at your own risk after thorough verification. Please note that we cannot be held responsible for any damages caused by the contents of this website.

Importing Solutions

By default, Dynamics 365 workflows do not allow batch processing, but by importing the “Change Tracking Solution” provided by Microsoft Labs, batch processing can be achieved.

Importing the Change Tracking Solution

Go to “Settings” and open “App Store”.

In the app search, search for Change Tracking Solution and click “Get it Now”.

Enter the required information and click “Continue”.

When the Marketplace page opens, select the instance you want to import. Select the instance you want to import, check the box, and click “Agree”.

The installation of Change Tracking will start, so please wait for a while. When the installation is complete, you are good to go.

Configuring Batch Processing for Workflow

Now let’s create a workflow for verification. In this section, we will describe how to run a workflow that leaves a note in the “Description” field that says “Provide details” every hour when the “Initial Communication” is “Contacted”. The following example shows how to do this.

Get Fetch XML from advanced search results

The batch process is configured to run only on the target records. Since Fetch XML is used to specify the target, we will prepare the Fetch XML in advance using advanced search results.

In this case, we will run the workflow only on records that have a value set to “Initial Communication,” so the filter condition is as shown below.

Click on “Download Fetch XML” to download the Fetch XML.

Creating a Workflow

Go to “Settings” and then “Process” to create a workflow.

Once the Change Tracking Solution has been imported, you will see “Batch Processes” displayed in the left panel of the workflow. This allows for batch processing of the workflow.

First, let’s set up the process. We created it as an on-demand process as shown in the figure below. *This setting is not required, as the process will automatically go into standby mode if you set the execution time of the batch process.

Save the file as overwrite. The next step is to set up batch processing.

Set up a batch process

Click “Batch Processes” and then “New Batch Processes”.

Enter an arbitrary name in “Name” and the workflow name mentioned above in “Process”.

The “Activation Frequency” can be set as shown below. The minimum unit is Hourly (every hour). In this example, we will select Hourly.

I set the “Status Reason” to “Scheduled” and the “Hours Interval” to “1”. In the “Next Activation” field, enter the time for the next activation.

Target Records" can be used to filter records and perform targeted workflow processing by attaching the contents of the XML file obtained from the advanced search results. Copy and paste the value of the Fetch XML file obtained above.

Save and close Batch Processes. Then “Activate” the process.

You are now ready to go.

Let’s first run the workflow we created on demand. When I open the lead, I see the following three records that I have prepared in advance. There are two records where “Initial Communication” is not yet set.

Select all of these to run the workflow created above on demand.

The “Description” section has been updated with on-demand workflow.

Confirmation of batch processing execution

Click “System Jobs” under “Settings”.

If you check, you will see that Batch Processes Scheduling is set to “Waiting for timer”, which means that the system job is created at the timing you set Batch Processes. The workflow created above will be processed every hour.

Changed the value of “Initial Communication” for one record before the process was executed.

Now when the time comes, the workflow should be executed only on the two records that contain the values.

Verify that the “Status” of the system job is “Successful” and check the “Process Session”. We have confirmed that the workflow is running on only the two target records.

When I checked the record, I found that the “Description” of the record where I had just changed the “Initial Communication” had been updated.

You don’t need to run it on demand

In the above example, for the sake of clarity, the workflow is executed on-demand for the record, but even if it is not executed on-demand, the “system job” will be launched and “waiting” at the timing when the Batch Processes is created.

If you want to stop the batch processing, just change the “Status Reason” to “Suspended” and save it.

Okay, that’s it for this time.