MS Dynamics CRM integration with ACC: RegionalDisco is disabled | Community
Skip to main content
L
LeonieSwart-lonalo
Level 2
June 11, 2021
Question

MS Dynamics CRM integration with ACC: RegionalDisco is disabled

  • June 11, 2021
  • 2 replies
  • 3083 views

Hi all

 

We have a CRM integration setup with our ACC environment.

We used the Office 365 deployment type.

 

As of 8/6 the integration stopped working and threw the following error: 'EnableRegionalDisco' is disabled

 

This is apperently because the RegionalDisco was deprecated by Microsoft.

I asked Adobe Support how we could fix this and they advised to change to serverUrl in the external account to: https://globaldisco.crm.dynamics.com/

After doing so the 'regionalDisco' error was gone but the integration wasn't working as we now face another error: GDS Resource Provider is unable to get instances for tenantId: XXXXX

 

Does anyone know what we are missing to get this up and running?

On Adobe, Dynamics or Azure side?

 

FYI: we are on build 9032

 

Edit: We got the integration working again by changing to the web-api deployment type. Needed to whitelist the serverUrl in the serverConf file and add a clientID to the configuration. 

We are still experiencing an issue when trying to use the configuration wizard to select tables from Dynamics:

 

 

Thank you

Leonie

 

 

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    2 replies

    U
    UoSDan
    June 14, 2021

    We have the exact same problem.

     

    We are currently in the process of attempting to reconfigure our connections to use app registrations and the Web API - although hitting stumbling blocks with this also as it requires changes to the URL Permissions on the serverconf.xml

     

    I've bookmarked this page and will confirm when we have a solution.

    L
    LeonieSwart-lonaloAuthor
    Level 2
    June 15, 2021
    Hi @uosdan
    LukasPe1
    LukasPe1
    Level 3
    June 15, 2021

    We also have the same problem.
    @leonieswart-lonalo where did you add the clientId? Could you give an example?

    L
    LeonieSwart-lonaloAuthor
    Level 2
    June 15, 2021

    Hi Lukas,

     

    We've added it to the configuration of the external account.
    When you select the web API deployment type it's an extra field that pops up.
    I requested the value of it from our Dynamics Team.

     

    The other credentials remained the same (of our previous Office 365 deployment type).

     

     

     

    Terms & ConditionsAccessibility statement

    Loading footer...