Dynamics 365和Azure集成 [英] Dynamics 365 and Azure integration
问题描述
我正在为Dynamics 365构建应用程序.
I am building an app for Dynamics 365.
应用程序应在潜在客户创建时触发，对外部服务进行HTTP调用，获取一些数据，并使用新数据更新潜在客户.
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.
我还需要在需要时通过从我方到客户实例对数据API进行HTTP调用来临时更新一条或几条潜在客户.
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.
此应用应该可以安装并在客户的Dynamics实例上运行.
This app should be installable and ran on a customer's instance of Dynamics.
据我所知，一种实现方法是使用Azure"Wep API"应用程序和Dynamics 365 OData Web API.
From what I gather, one way to do this is to use Azure "Wep API" app and Dynamics 365 OData Web API.
使用文档和MSDN 3天后，我对以下问题没有任何答案，因此我需要在这里为您提供帮助.
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.
我的问题是:
-
我将如何实施触发器以对潜在客户创建或更新进行某些操作? (类似于插入触发器之前的SF)
How would I implement a trigger to do something on lead creation or update? ( similar to a SF before insert trigger )
每秒/分钟/天在外部发出的HTTP请求数量是否有限制?
Are there any limitations on the number of HTTP requests made outside per second / minute / day?
我可以批量更新销售线索的HTTP请求数量是否受到限制?
Are there any limitation of the number of HTTP requests I can make to update leads in bulk?
运行时间是否有限制?
我无法找到任何文档，老实说，我对整个MS云生态系统的复杂性和混乱感到震惊，所以请帮助:)
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 :)
推荐答案
我找不到与此有关的任何文档，老实说，我 整个领域的巨大复杂性和混乱让您震惊 MS云生态系统
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制造了很多软件，知道您需要哪些位是一半的挑战.有关文档，请尝试此处.
- 这些软件虽然经常以包装"的形式出售或呈现，但它们通常是完全独立的应用程序.
- 看来您在看； Microsoft Dynamics 365 (以前称为CRM)和
- 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.
关于Microsoft Dynamics 365的特定要点:
Regarding your specific points for Microsoft Dynamics 365:
Workflow with a custom workflow activity, or a plugin is a good option.
我不相信.
取决于.总的来说没有.如果您使用的是 ExecuteMultipleRequest ，那么是的，上限为1000
Depends. In general no. If you are using ExecuteMultipleRequest, then yes there is a limit of 1000.
是的，如果您正在沙盒中运行>.
Yes, if you are running in the sandbox.
Microsoft Dynamics 365(在线和本地)支持执行 隔离环境中的插件和自定义工作流程活动.在 这种隔离的环境，也称为沙盒...如果沙盒 承载此自定义代码的工作进程超过了CPU阈值， 记忆，处理限制或以其他方式无响应 将被平台杀死.
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.
这篇关于Dynamics 365和Azure集成的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
