Asynchronous Batch Process Solution Revisited – part 4

In the previous post, I walked through the ABP (Asynchronous Batch Process) Aggregative Query Scenario. In this post, last in this series, I’ll go through the External Action scenario.


1. Download the Asynchronous Batch Process Solution, import into Microsoft Dynamics CRM 2015 on-premise/Online organization
2. Go to Settings – > Solutions and Open the ABP solution. Go to the Batch Process entity definition and check the Settings checkbox in the ‘Areas that display this entity’ section
3. Save and publish the solution

As always, I advise against publishing any external solution on your production environment without testing it first.

External Action scenario

This scenario describes a scheduled action, not necessarily related to Microsoft Dynamics CRM records, hence external.
The target records FetchXML query can be used but it is optional.
This action is usually a wrapper for Custom Workflow Activity performing some magic which the native process tools can not.

Some sample business requirements of this type:

– Retrieve users data from AD (Active Directory) on daily basis and update Microsoft Dynamics CRM users data accordingly
– Import/export data to/from Microsoft Dynamics CRM to an external application over night
– Generate and email SSRS report to a mailing list every month

Following are the steps to implement the daily AD users data synchronization. For this scenario I assume you already registered a Custom Workflow Activity with some capability to retrieve data from AD and update System User records.

1. Create a new Action targeting ‘None (global)’ and name it ‘Synchronize AD users’
2. Add a step to activate the AD synchronization Custom Workflow Activity component
3. Save and activate the process


4. Create a new Batch Process record (Settings –> Batch Processes)
5. Name the Batch Process: ‘Daily AD users synchronization’ (or other meaningful name)
6. Set the Activation Frequency to ‘Daily’
7. Set the Process field value to ‘Synchronize AD users’ process
8. Set the Next Activation to any future date and time. I suggest selecting the application’s least busy time
9. Set the Status Reason to ‘Scheduled’
10. Click Save to schedule the Batch Process


You are done! The Batch Process is set and waiting for the next activation date and time. If all goes well, the AD users
synchronization will execute as defined and the Batch Process will reschedule to the same time next day.

If you would like to deactivate the Batch Process scheduling, change the Status Reason value to ‘Suspended’ and save. Since there may already be a Workflow instance scheduled and waiting, go to the Background Processes for the Batch Process record and cancel waiting instances.
This also applies if you change the Next Activation date/time once the Batch Process record is already created and scheduled.

I hope you find the scenarios I have described in the series as useful to you. If you have development skills or resources, you can customize the ABAP solution as you like, the source code is available on CodePlex.
I will keep adding features to this component and upgrade along with Microsoft Dynamics CRM versions until MS supplies a similar built in solution.

Microsoft Dynamics CRM On Edge

I don’t usually blog about these topics, but I feel Windows 10 and the Edge browser justify it. Also, I need a little break from the ABP related posts.

Just upgraded my old laptop from Windows 7 to Windows 10 Enterprise. In the past, I have decided to skip Windows 8 altogether because it  made me feel like a fish out of the water and an unproductive one at it.

Windows 10 feels right to me.
It upgraded smoothly in about 1 hour and It runs great on my weak (3GB RAM, 2.4GHz dual core) laptop. The UX is very friendly and I know where to find everything.
Although I have only skimmed Windows 10, I feel I won’t regret upgrading.

The new Edge browser looks good. Clean and functional UI with good performance. Haven’t compared properly yet, but it feels at least as fast as Chrome, and like Chrome it uses multiple processes.

The best news, is that Microsoft Dynamics CRM (Online, RU 0.1) is running smoothly on Edge. No error messages, good performance (especially compared with IE).
This shouldn’t be taken for granted. As far as I can remember, no new version of IE could run Microsoft Dynamics CRM application from day one, without some adjustments made in IE browser, Microsoft Dynamics CRM application or both.

So in the next few days, I will be wearing Microsoft Dynamics CRM on Edge. I am looking forward to make Edge my default browser.

Microsoft Dynamics CRM 2015 on Edge browser