Dynamics CRM 更改状态工作流程错误
我有一个工作流程，该工作流程运行以将案例记录的状态更新为“已解决”。但是，工作流进入“等待”状态并包含一般错误消息。查看系统作业消息时，它显示：
这已在另一个系统上运行（因为我所做的只是更新状态）所以我认为它与适当的自定义有关。
有其他人遇到过这个问题吗？您是如何解决的？
提前致谢
更新：
我已经创建了一个新组织来测试任何可能的解决方案并缩小可能发生的情况的范围。
我在空白组织上创建了一个工作流程和一个测试用例记录来进行尝试。正如预期的那样，它工作得很好。
然后，我导入了客户系统上的自定义设置。又做了同样的事情，效果很好。
然后我创建了一个新的案例记录并尝试了原始的工作流程，但这不起作用。
然后，我添加了一个与第一个工作流程相同的工作流程，并在预自定义记录上进行了尝试，它起作用了。
然后我在新记录上尝试了新的工作流程，但再次不起作用。
因此，工作流程似乎无法处理自定义导入后的任何记录。
以前有人遇到过这种情况吗？采取了哪些步骤来解决？
再次感谢
I have a workflow that that runs to update the status of a Case record to Resolved. However, the workflow gets put into status 'waiting' and contains a generic error message. When looking at the system job message it says:
This has worked on another system (as all I am doing is updating a status) so I assume it has something to do with the customizations in place.
Has anyone else ever come across this and how did you resolve it?
Thanks in advance
UPDATE:
I have created a new organisation to test out any possible solutions and to narrow down what might be happening.
I created a workflow on the blank organisation and a test case record to try it out on. It worked fine as expected.
I then imported the customizations that are on my customers system. Did the same again and it worked fine.
I then created a new case record and tried the original workflow, this did not work.
I then added a workflow that does the same as the first workflow and tried it on the pre customizations record, it worked.
I then tried the new workflow on the new record and once again this did not work.
It is therefore appearing that the workflows are not working on any records post customization import.
Has anyone come across this before, and what steps were taken to resolve?
Thanks again
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果您可以查看已注册的插件，请搜索在实体案例（事件）的消息
SetState或SetStateDynamicEntity上注册的插件。我假设有一个插件在您的情况下失败了。这就是您的错误消息的原因。
If you have the possibility to look at the registered plugins, then search for a plugin registered on the message
SetStateorSetStateDynamicEntityfor the entity case (incident).I assume there is a plugin which fails in your case. This is the reason for your error message.