Expand my Community achievements bar.

Announcing the launch of new sub-community for Campaign Web UI to cater specifically to the needs of Campaign Web UI users!
SOLVED

Internal working of CRM connector.

Avatar

Level 3

Hi all,

I am looking for 2 things:

1. Does anyone happen to know the internal working of CRM connector. What I am particularly interested in knowing is how the querying is done from the server            database and is there any involvement of "ServiceURL" in this process.

2. Does anyone know where can i find the "ServiceURL" being used in CRM connector ?

The reason behind these questions is we have been facing a crmConnector timeout error. And the client is asking for the "ServiceURL" for investigating on their part.

Any help on finding the "ServiceURL".

Kindly refer the screenshot below for the error.

crm.JPG

Regards,

Jayesh

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi,

MS Dynamics connector uses a variety of URL's, which can be found in crm:mscrmConnector.js, and partially in your config above. If you're debugging the calls, the easy approach is to put a mitm proxy between the wfserver and the internet and capture what's triggering the 500 response. More difficult would be to wrap the ootb request functions with logging calls and then swap them into the crm code.

Thanks,

-Jon

View solution in original post

5 Replies

Avatar

Community Advisor

Hi.

The URL varies on the CRM you're connecting to. That error says 'SQL timeout', with the HTTP call being a 500 error, so this doesn't sound like a connectivity issue. Which CRM is this?

Thanks,

-Jon

Avatar

Level 3

Hi Jon,

PFB screenshot of the External account configuration used for CRM connector. We are using Microsoft Dynamics CRM. Can you tell me where/ how can I find the "ServiceURL"?

crm.JPG

Regards,

Jayesh

Avatar

Correct answer by
Community Advisor

Hi,

MS Dynamics connector uses a variety of URL's, which can be found in crm:mscrmConnector.js, and partially in your config above. If you're debugging the calls, the easy approach is to put a mitm proxy between the wfserver and the internet and capture what's triggering the 500 response. More difficult would be to wrap the ootb request functions with logging calls and then swap them into the crm code.

Thanks,

-Jon

Avatar

Level 3

Hi,

Could you give more information on the second way ("More difficult would be to wrap the ootb request functions with logging calls and then swap them into the crm code.")? What steps need to be followed to do this?

Regards,

Jayesh

Avatar

Community Advisor

HI,

As I said, it's the hard way:

  1. Create a custom addMethod function with the same interface as HttpSoapConnection's addMethod
  2. Have new addMethod call HttpSoapConnection's addMethod, then replace the function it creates with code that calls the replaced function while logging its inputs and outputs
  3. Change crm connector code to use instrumenting addMethod instead of old one

Thanks,

-Jon