CRM 2011达到最大深度 [英] CRM 2011 Maximum depth reached

问题描述

我在CRM中有一笔交易，交易正在达到最大深度(8)，这是一个非常复杂的插件链，并且企业需要以此方式进行此操作.

I have a transaction in CRM and it is reaching its maximum depth (8), it is a very complex chain of plug-ins and the business requires this operation in this way.

将最大深度从(8)更改为(16)是一个好选择，因为我们的业务需要，或者由于达成了很多逻辑，我们不应该做某些事情.

Is it a good option to change the maximum depth from (8) to (16) because our business requires or there is something that we should not do because there is a lot of logic being reached.

我之所以这样问，是因为微软表示此限制是为了检测无限循环.

I asking this because Microsoft says this restriction is to detect infinite loops.

我想问微软这个问题，但是微软为我们服务的这个人存在利益冲突，因为他们想要我们拥有相同的客户，因此，如果我们为我们的CRM建议这一点，他们将想知道哪里出了问题.专注于为我们找到最好的解决方案.

I want to ask Microsoft this, but this person that Microsoft has for us has a conflict of interest, because they want the same client we have, so if we suggest this for our CRM they will want to see what is wrong instead on focusing for the best solution for us.

在此先感谢您的光临.

推荐答案

我们决定按实体和消息对插件进行分组.

We decide to group the plug-ins by entity and message.

因此，如果我们有一个插件 foo 过滤new_field1，而另一个插件做 bar 过滤new_field2，则我们将两个插件合并为一个.

So if we had one plug-in foo filtering new_field1 and another plug-in doing bar filtering new_field2 we merged both plug-ins in one.

注册了第一步，过滤了两个字段，并且实现处理何时调用foo，bar或两者.

One step was registered filtering both fields and the implementation handles when to call foo, bar or both.

这样，我们可以减小深度.

This way we reduce the depth.

这篇关于CRM 2011达到最大深度的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！