Asynchronous Batch Process Solution Revisited – part 4

Sunday, August 30, 2015

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. Prerequisites 1. Download the Asynchronous Batch Process Solution, import into Microsoft Dynamics CRM 2015 on-premise/Online organization2. 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’ section3. Save and publish the solution As always, I advise against publishing any external solution on your production environment without testing it...

Asynchronous Batch Process Solution Revisited – part 3

Monday, August 10, 2015

In the previous post, I walked through the ABP Target Records Scenario. In this post, I’ll go through the Aggregative Query Scenario. Prerequisites 1. Download the Asynchronous Batch Process Solution, import into Microsoft Dynamics CRM 2015 on-premise/Online organization2. 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’ section3. Save and publish the solution As always, I advise against publishing any external solution on your production environment without testing it first. Aggregative Query Scenario ...

Asynchronous Batch Process Solution Revisited – part 2

Sunday, July 26, 2015

In my previous post, I described some of the Asynchronous Batch Process Solution (ABP) version 2 internals. In the next posts, I would like to go through different business scenarios and explain how to use the ABP solution, step by step. Prerequisites 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...
no comments

Asynchronous Batch Process Solution Revisited – part 1

Sunday, July 19, 2015

I had some free time and decided to review the Asynchronous Batch Process Pattern Solution. On January 2013 I promised to publish a revised version and didn’t manage to do so. To redeem myself, I have decided to publish this version on CodePlex, so it can be customized by anyone who needs to. If you don’t know what ABPP is all about and what’s in it for you, I suggest you start here. In the first part of this post I’ll describe the new features, architecture considerations and implementation details. In the next part, I’ll walkthrough the different scenarios and use...

Asynchronous Batch Process Pattern – Leveraging December 2012 Service Update (Polaris) Features

Wednesday, January 30, 2013

December 2012 Service Update features two new interesting capabilities: Custom Activities support for Microsoft Dynamics CRM Online Executing multiple requests with the ExecuteMultipleRequest class   These capabilities allow important improvements to the Asynchronous Batch Process Pattern solution described here. So what’s new? The lack of Custom Activities support in Online deployment required the usage of a Plugin component to perform the Target Records query and implementing the Action Workflow to each result record.   With December 2012 Service Update Custom Activities support for...

Reviving Microsoft Dynamics CRM 2011 Activities using Process

Monday, December 31, 2012

Microsoft Dynamics CRM 2011 UI does not enable users to reactivate Activities. Once an activity such as Task is completed, it can not be re-opened, although users may add notes and attachments to it. I can think of a business scenario in which a user is required to reactivate a Task. Maybe it is incomplete although reported as completed, or maybe reported completed by mistake. In this scenario, a Process can be used as Processes can change completed Task state from ‘Completed’ to ‘Open‘. You can set a manual Workflow rule to do just that....
one comment