Interested in a ServiceNow event built for developers? Registration for now[dev]26 is officially open!

Failing to establish ServiceNow integration with Microsoft Dynamics 365 CRM

ritik-rajen
Tera Contributor

Hello,

 

I'm trying to establish a connection between ServiceNow and Microsoft dynamics 365 CRM. We are using spokes in this case.

 

Client id and secret we got from dynamics team and with all the Application registry followed by oauth profile & scope as well as Connection and credentials, everything is correct. In credentials we are able to get Oauth token basically "successful" which expires after an hour.

 

Now we are using the same data (default connection) in "Update Record" action in flow. 

 

Issue which I'm facing right now.

 

1. Oauth Scope and Profile is coming as empty. If I try to manually populate it then on the first click on "Save and get OAuth token" button, it shows an error which will be visible in snapshot (which I will share) in bottom right corner. If I click the second time on "Save and get OAuth token" button, it goes successful and the page loads again and I can see again the Oauth profile and scope is empty. (this is all when we click on pencil icon in flow on Update Record action). One more thing, this I tried in 2 different instances by enabling spoke and in both the cases, oauth profile and scope was empty. 

 

2. I'm also getting an error in same action (which will be visible in same snapshot): Unable to load Dynamics input and other error as well.

 

So anybody faced similar issue, if yes then how did you resolved it?

 

 

ritikrajen_0-1790182728007.png

 

 

 

1 REPLY 1

Tanushree Maiti
Tera Patron

Hi @ritik-rajen 

 

You can try with following troubleshooting options:

 

1. Clear your instance cache using cache.do and then test once your integration.

2. Have you used Mid server for this integration. Ensure Mid server is up.

3.  Check with your internal network security team to verify if outbound traffic to Microsoft Dynamics services is permitted or blocked by a proxy or firewall rules.

 

4. https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2516399

 

 

 

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti