CRM 2013 – Workflows – Schedule workflows using ISV Provider North52

We’ve requirement to schedule workflows to run at certain times/dates. The workflows can be created in CRM and then run by a console tool or something by a Windows schedule service.

We have used Windows Service or Scribe Insight to trigger workin some project and it works as expected. Today we will introduce another CRM tool N52 which is highly configurable and easily setup.

Below are the steps to set up the workflow schedule by using N52:


1. Download N52 solution from North52 website:

2. Import the N52 solution into CRM:

North 52-1

3. Create an on-demand workflow on account entity which is used to send notification on daily basis:

North 52-CRM-2

4. Create a new N52 Schedule from N52 menu. You can specify the workflow to be executed; Select the frequency, start date time and end date time. The Fetch XML query is required to retrieve the records:

North 52-3

5. Start Schedule:

North 52-4

6. After the workflow is triggered, you can review the running status in N52 Schedule tab:

North 52-5


I hope you find it useful!

Author: Zhe Chen
Title: Lead Dynamics CRM Consultant @ Adisys


CRM 2013 – Reports – Avoid updating reports on Reporting Server Directly!

Dynamics CRM reporting service supports automatic data Pre–Filtering to

  • Make reports context-sensitive by narrowing the scope of a report to return more relevant data.
  • Retrieve and display a result set faster because only more relevant data is returned.
  • Allow the report to be filtered using the Advanced Find feature.

To enable automatic data pre-filtering on a report, you can alias entity tables in queries by using an alias name that starts with “CRMAF_”.


Here is one reference you can take a look at:


When CRM administrator deploys the report RDL in Dynamics CRM solution, CRM automatically modifies the uploaded RDL code to add “p1” parameter and modify the query. It works very well and Pre-Filtering will be enabled for this report.

CRM Reports

Figure 1: Uploading RDL in CRM Solution


Report Parameters

Figure 2: CRM Automatically added Parameters


However sometime report administrator might go to Reporting Server and deploy/modify the RDL on server directly which might cause the CRM automatically added code lost. It’s difficult to troubleshooting the issue until you realize the RDL code was modified by CRM when uploading the report.

To avoid this kind of potential issue in our project, we always deploy and update the custom report through CRM and avoid the direct modification on reporting server.


I hope you find it useful!

Author: Zhe Chen
Title: Lead Dynamics CRM Consultant @ Adisys

CRM 2013 – Business Process Flow – Disable the fields on process bar

Dynamics CRM 2013 BPFs have many beneficial qualities.  They are available for both OOB and custom entities, can span across multiple entities.

When a form displays a business process flow control in the header, additional controls will be added for each attribute that is displayed in the business process flow. These controls have a unique name like the following: header_process_<attribute name>.

Controls displayed in the form header are accessible and have a unique name like the following: header_<attribute name>.

CRM Process bar

CRM Process bar

We have requirement to disable the fields on process bar based on some logic. Below is the Java Script code to implement it:

var c = Xrm.Page.getControl(“header_process_xxxxxxxx”);  //Get the field from process bar

if (c!= null) {



CRM Process bar

CRM Process bar


I hope you find it useful!

Author: Zhe Chen
Title: Lead Dynamics CRM Consultant @ Adisys