简体   繁体   English

将CRM动态升级到Prem 9.0.5之后的bpf错误

[英]bpf error after upgrade crm dynamics to on prem 9.0.5

after successfully upgrade to dynamics from 2016 8.1 to 9.0.5 on prem, 成功将动态版本从2016 8.1升级到9.0.5后,

we encountered a problem with business process flow, 我们在业务流程中遇到了问题,

as we know each bpf has its own entity in the DB, 我们知道每个bpf在数据库中都有自己的实体,

we use an OOB bpf in incident entity that called phonetocaseprocess, 我们在称为phonetocaseprocess的事件实体中使用OOB bpf,

the problem is that i saw after the upgrade that the newly table created for 问题是,我在升级后看到新表为其创建的

that bpf - is empty :() , so all the current incidents failed on update because 该bpf-为空:(),因此所有当前事件均在更新时失败,因为

i get an error that said that : phonetocaseprocess With Id = 196dc1e2-466f-e911-80e6- 00155dc4022d Does Not Exist. 我收到一个错误消息,说: id不存在phonetocaseprocess 196dc1e2-466f-e911-80e6- 00155dc4022d。

when i create a new incident record it works fine and a record is created in 当我创建新的事件记录时,它工作正常,并且在

phonetocaseproccess table. phonetocase处理程序表。

someone encountered that? 有人遇到过吗? or have an idea? 或有一个主意? thank you 谢谢

UPDATE 更新

we were able to resolve this by running the script provided in the above forum before the upgrade run, after this the upgrade was successfully completed. 在升级成功完成之前,我们可以通过运行上述论坛中提供的脚本来解决此问题。

https://community.dynamics.com/crm/f/microsoft-dynamics-crm-forum/232669/business-process-flow-instance-exists-error-after-crm-2016-upgrade/639024 https://community.dynamics.com/crm/f/microsoft-dynamics-crm-forum/232669/business-process-flow-instance-exists-error-after-crm-2016-upgrade/639024

The problem occurred because processes in the source environment did not have a unique name in the database, which resulted in the upgrade not converting the data to the correct table in the DB but to another table in new_bpf_guid format. 发生问题的原因是源环境中的进程在数据库中没有唯一的名称,这导致升级未将数据转换为DB中正确的表,而是转换为new_bpf_guid格式的另一个表。

hope this will help someone 希望这会帮助某人

That's because your existing records are related to the older process and that the process in the newer version has different GUID. 这是因为您现有的记录与较旧的流程相关,并且较新版本中的流程具有不同的GUID。 See the snapshot below: 请参见下面的快照:

在此处输入图片说明

To correct this, you have to migrate the process entity data with the existing primary keys in the older version. 要解决此问题,您必须使用旧版本中的现有主键迁移流程实体数据。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM