CODEWITHSUNDEEP
azuredynamics-crmintegrationmicrosoft-dynamics
Assaf Moldavsky
Assaf Moldavsky

Reputation: 1721

Dynamics 365 and Azure integration

I am building an app for Dynamics 365.

The app should trigger on lead creation, make an HTTP call to an external service, get some data, update the lead with the new data.

I would also need to update single and a batch of leads ad-hoc when needed from my service by making an HTTP call to the data API from my side to the customer's instance.

This app should be installable and ran on a customer's instance of Dynamics.

From what I gather, one way to do this is to use Azure "Wep API" app and Dynamics 365 OData Web API.

After 3 days of going to the docs and MSDN I do not have any answers to the following questions so I need the help you the good folks over here.

My questions are:

  1. How would I implement a trigger to do something on lead creation or update? ( similar to a SF before insert trigger )

  2. Are there any limitations on the number of HTTP requests made outside per second / minute / day?

  3. Are there any limitation of the number of HTTP requests I can make to update leads in bulk?

  4. Are there any limitation on the running time?

I was not able to locate any documentation on this and to be honest I am blown away by the sheer complexity and confusion around the entire MS cloud ecosystem, madness... so please help :)

Upvotes: 1

Views: 607

Answers (1)

James Wood
James Wood

Reputation: 17552

I was not able to locate any documentation on this and to be honest I am blown away by the sheer complexity and confusion around the entire MS cloud ecosystem

This question is perhaps a little too broad. A couple of pointers:

  • Microsoft make a lot of software, knowing which bits you need is half the challenge. For documentation try starting here.
  • These bits of software whilst often sold or presented as a 'package', are usually quite separate applications.
  • It seems you are looking at; Microsoft Dynamics 365 (previously known as CRM) and Azure (which itself is composed of dozens of sub services).
  • I suggest you start by learning about each application, and then move onto integrating them together. For 365 I have a blogged a series of articles you may find useful.

Regarding your specific points for Microsoft Dynamics 365:

  1. Workflow with a custom workflow activity, or a plugin is a good option.

  2. I don't believe so.

  3. Depends. In general no. If you are using ExecuteMultipleRequest, then yes there is a limit of 1000.

  4. Yes, if you are running in the sandbox.

Microsoft Dynamics 365 (online & on-premises) support the execution of plug-ins and custom workflow activities in an isolated environment. In this isolated environment, also known as a sandbox...If the sandbox worker process that hosts this custom code exceeds threshold CPU, memory, or handle limits or is otherwise unresponsive, that process will be killed by the platform.

Upvotes: 1

Related Questions