Lessons learned: Using Resco Mobile CRM as front end with Dynamics CRM/365 as back end


I have been working many years now with Resco Mobile CRM. Using it as an alternative for the Dynamics CRM mobile client. Resco does have some nice advantages over the default mobile application, but also has some drawbacks, which I sometimes painfully learned. If you are planning to go full on Resco Mobile CRM, using it as a front end instead of Dynamics CRM/365, I would like to share some lessons with you. To be clear: I’m talking about Resco Mobile CRM as the mobile application (not the standalone CRM software which is called Resco Cloud).

Lesson #1: Double the software, double the work!


Resco Mobile CRM does take over custom fields you might have created in Dynamics CRM/365, but you will still have to activate these fields in Woodford (which is the configuration tool for the Resco Mobile CRM client). Next, if you have created business rules Dynamics CRM, you will need to create ‘Rules’ on the forms in Woodford, simulating the same business intelligence you might have created in Dynamics. Same thing with views, graphs and dashboards you might have created personal or system-wise.

So don’t forget that you’ll have to do everything twice if you use Resco Mobile CRM in the front end (e.g. for salespeople on the road) and Dynamics CRM/365 in the back end (e.g. for sales support staff in the office).

Resco’s feedback:

The idea behind “double” setting of the Resco Mobile CRM app, is that not all entities and fields, are used by user on the mobile device. Since there is also a possibility of an offline mode to build up the local database, the Resco Mobile CRM app only uses enabled entities and fields, to save space on the device and data during synchronization, since only entities and fields, relevant to the mobile use of CRM, are actually used.

When it comes to business logic, to provide the full experience, user will need to work in online mode, since workflows and processes, plugins, may require access to entities, fields, records, that are not available in offline mode, and could cause severe issues. And again, usually not all business logic is required for mobile users, and there is a need to provide different logic for mobile use. So, if there is a need to use a logic in offline mode, or even in online mode, during work with data, Rules and JavaScript is available. Rules are a powerful tool, to provide control over forms, and entered data, while the editor is similar to CRM workflow editor, and you can reuse the JavaScript used on the CRM server directly in the Resco Mobile CRM app, without any changes, if needed.

Lesson #2: Business process flows will give you trouble!


You can activate the business process flow (BPF) from Dynamics CRM/365 in Woodford, allowing to copy the BPF to the Resco mobile client. However, you have virtually zero control over the behavior of this BPF in Resco. You want to hide a field in the BPF, based on a value in another field? No luck, the ‘rule’ you wrote in Woodford has no influence on it. You want to change the lookup filters on a field in the BPF? Again no luck, you can modify every lookup in Woodford, except for the fields in the BPF.

My advice: Just use spacers with the same text binding as the stages from your BPF and  built your mobile form in the same stages.

Resco’s feedback:

On the other hand, we use Business Process Flows (as only process) completely from the CRM server, as is, so all changes to this process are to be made on the CRM server. It is possible to e.g. fill in fields using Rules, but to change the logic, it is to be done on the CRM server side, by adjusting the Business Process Flows for both – CRM backend and the Resco Mobile CRM app. However we plan to add an option to manage Business Process Flows using Rules or JavaScript in the future, to allow the required functionality.

Lesson #3: Security, security, security!

Field properties.png

Microsoft Dynamics CRM/365 has several levels of security you can play with as a system administrator; Business units, security roles, field security roles, … . Resco however, builds upon all these security levels and adds its own security. So you should take a moment to get acquainted with the new playbook of security:

  • Resco uses RCU (Read, Create, Update) permissions on fields.
  • Resco allows you to pick different Dynamics CRM security roles to allow users to use a mobile application. However, it does not do anything else with these security roles.
  • Resco has a “security” tab in Woodford, but this only gives you an overview of which devices are connected with your organisation. Moreover, it allows you to lock, wipe or force a full sync of the mobile device.

Resco’s feedback:

If a user does not have permission to access certain records, entities, we in Resco are not able to grant the user access to forbidden records, entities. From the CRM security part, we are not supporting only the Field permissions (can be easily done using Rules), but Business Units, Security Roles, Security Role Permissions are of course used as on the CRM server, since the CRM server will not provide data, that the user does not have permissions for.

  • Resco uses RCU (Read, Create, Update) permissions on fields.
    • This is an additonal permissions, to narrow down user’s options if you want to disable e.g. filling up a certain field on the Mobile CRM application.
  • Resco allows you to pick different Dynamics CRM security roles to allow users to use a mobile application. However, it does not do anything else with these security roles.
    • Of course it does, as described in the above paragraph, CRM server will not allow accessing to different data, than those, that the user has permissions for. Otherwise it would not make sense of course.
  • Resco has a “security” tab in Woodford, but this only gives you an overview of which devices are connected with your organization. Moreover, it allows you to lock, wipe, or force a full sync of the mobile device.
    • Again, it is an additional security option, a part of the Mobile Application Management, that allows administrators to manage access to CRM data on the device level, to create security policy to allow or disallow certain device (or new, that need to be allowed after verification) accessing CRM data using the Resco Mobile CRM app, and to set up lock or wipe immediately to Resco Mobile CRM app on one, or group of devices, or automatically Lock or Wipe the app after the app has not been in contact with server (e.g. after being lost, stolen) after certain time, or after entering CRM user’s password several time.

Lesson #4: Adding business intelligence to Resco through workflows in Dynamics

So lets say you have created a workflow in Dynamics CRM/365 to do action X (e.g. create a task) when trigger Y (e.g. a value in an option set changes) happens. The business intelligence will execute as next:

  1. You change the option in the option set in the mobile client of Resco.
  2. Depending on whether or not your working online: If you are working online, than the change will directly be synchronized to the Dynamics CRM/365 and the workflow will be activated. If you are working offline, than the change will be saved in the offline database of Resco Mobile CRM. If you go back online, the modification will be synchronised to the Dynamics database.
  3. The workflow is executed and creates the task
  4. The task is synchronised back to the mobile client.

But lets mix things up and say you want to create an “on demand action” in Resco Mobile CRM. Then you are in for some action! E.g. I want to allow users to add accounts to a custom queue. This queue is designed for accounts which need to be checked for errors or incomplete data.

  1. Create an option set (related to a general option set) in Dynamics CRM/365. We will pick an option set, because we want to be able to execute multiple workflows.
  2. Create a workflow in Dynamics CRM/365. Trigger for the workflow is ‘On Change’ of the option set you created in the first step.
  3. Create a custom command in Woodford. This command will ‘On Execute’ pick an option of your option set. So when the option is picked, the workflow will be triggered.

Lesson #5: Resco has some tricks in their sleeve, which Dynamics CRM/365 does not have (yet)

The last lesson I want to share for now, is that using the Resco Mobile CRM front end offers some specific tricks, which you should exploit as best as possible:

  • One of the reasons customers want me to implement Resco, is because it offers offline capability. This is one of the features which Microsoft is working hard on.
  • Another nice feature, is the unified User Interface Resco has. It does not matter if you are using Resco on a mobile device or on a desktop. You did know you could run Resco as a program on your desktop, did you?!
  • Resco had the capability to map accounts, contacts, leads on a global app. And then use the locations of these records to make route plans between the records. Moreover, you can then use route plan for your GPS.

Finally, I hope you learned something from the lessons I shared with you. If you have some things you want to share from your adventures with Resco Mobile CRM and Dynamics CRM/365, feel free to comment on this blog post!

Note: after publicizing this post, I had some very good feedback of the wonderful support team of Resco Mobile CRM. As I’m pro freedom of speech, but also pro right of reply, I have added Resco’s clarification to the different lessons. You will find this under “Resco’s feedback”.


  1. Eric Dickinson

    What are your thoughts on the Dynamics Field Service app (2017) that runs on the resco platform? I cant seem to find a difference bewtween the two other than the Dynamics version has some bugs in it.

    1. Koen vdv

      Hi Eric,

      in my opinion; the Dynamic Field Service app is a first ‘draft’ of how the Field Service business could be supported by a mobile application.

      Microsoft did an offer to buy Resco, but the offer was rejected and instead the Resco-software was sold (Resco as Mobile Development solution). This brought us the Dynamics Field Service app, together with the Field Service application.

      However, with the arrival of PowerApps, I’m guessing that all the investments are now going to other solutions and I would not be amazed if the Dynamics Field Service app would disappear quietly from the stage.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.