19 May’16

Dynamics CRMDebug Script on Tablet/Mobile Application


After the release of Microsoft Dynamics CRM update 1, Microsoft has removed the mobile version of form and made actual form available for the Mobile/Tablet. But, since few scripts do not work on mobile/Tablet, and work fine on the Browser, Microsoft has released the guide line that should be followed while writing the scripts.

Kindly refer the below link for further details on the guide lines provide by Microsoft.


There are scenarios where scripts break and we are not able to debug them on phone/Tablet. Which leads to no proper error tracing by the developers.


The script which worked perfectly fine on the Web Browser, had issues on phone/Tablet. These scripts sometimes have more than thousand lines of code and we struggle to find what exactly is causing it to fail. Microsoft, for the same reason has now come up with a solution to debug these scripts.

Follow the below steps in order to debug:

Step: 1
While writing script makes sure to include the ‘debugger;’ tag in the beginning of the function or where you want to debug the code.

Step: 2
Create a URL which works same as that of tablet.

Step: 3:
For e.g. the organization URL will look like below.

Unique name of the org can be obtained from Settings -> customization -> developer resource -> unique name

Before opening the above mentioned URL make sure you are already logged in the web browser else the link will not work.

Step 4:
You will receive the below message whenever there is a change in the customization.

Makes sure to download the latest changes, it will take few seconds.
Step: 5
Once the download is completed you can test your script by pressing F12 button, in our case I have registered the script on change of Phone field as you can see below.

As soon as the value of Phone field changes it takes me to the debugger line. (PFB the screen shot for the same)

Using this approach, you can debug the script on the desktop using the tablet version of CRM.


We can debug the mobile version of script on the web browser by the steps provided. Which will allow better debugging than the manual one that the legacy system had.


Written by

Team Member


Leave a Reply

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

Time limit is exhausted. Please reload the CAPTCHA.

Want to streamline your business processes?

  • This field is for validation purposes and should be left unchanged.

Recent Articles

  • Reading more then 10K records in D3FOE OData API

    11 July’ 2018

    Introduction: We all know Dynamics 365 Finance and Operations has limitation of 10K records to be fetched at a time usi...

    Read more
  • Paging in D365 Customer Engagement v9.0

    10 July’ 2018

    Introduction: The Xrm.retrieveMultipleRecords method is used to retrieve a collection of records in Dynamics 365 Custom...

    Read more
  • Set up Dynamics 365 connection in Microsoft Social Engagement

    10 July’ 2018

    Introduction: This blog explains how to Set up Dynamics 365 connection in Microsoft Social Engagement. Steps to be follo...

    Read more
  • Voice of the Customer failed to install

    10 July’ 2018

    Introduction: Many people face issues in installing Voice of Customer solution on v9 environment and trying repeatedly ...

    Read more
  • Scribe Insight AX as a Web Service Find Block issue

    10 July’ 2018

    Introduction: If we need to look up for any value from AX then we do it by using a Find Block in Scribe Insight Eg: Basi...

    Read more