There is one traditional method where you remove/disable some function calls and try to see where the error is coming. Then put some alert messages to identify where the error is coming. Well, this process is very time consuming since after every JS change, you need to close the MoCA app, start again, it will download the customization again. I mean very frustrating.
The other approach we can think of if there is any way, we can take advantage of developer tools capability to identify where the problem is and what we can do to solve the issue. Fortunately the answer is yes.
Below are the steps you need to take to identify how to do fixes in MoCA. Suppose you have external URL configured as https://orgname.crm.com:
- Open the browser and enter external URL as https://orgname.crm.com
- Authenticate the URL and it will take you to CRM web version home page.
- Open another tab in the same window and enter the URL after making changes as below:
4. It will open the MoCA app in browser and you are done.
The URL mentioned in Step #3 is nothing but NGA web service URL that is used by MoCA app to connect with CRM server.
Hope it should help CRM developers to debug scirpts in MoCA and save lot of time. Please comment and share so that it will reach out to larger audience.