如何使用特定 GUID 创建新记录
我正在尝试使用 Dynamics CRM 创建实体的实例。 我想手动设置 GUID，但如果我的属性是 DynamicEntity 的主键，则会出现以下错误。
服务无法处理请求
我正在构建 DynamicEntity，并且设置 [entityname]id 属性会导致请求失败。 它在两个 CRM 实例之间移动数据，因此如果有人知道在 CRM 之间复制记录的更好方法，那也是可行的。 否则，我希望 GUID 能够跨实例匹配...因为这就是 GUID 的要点。
Using the Dynamics CRM I'm trying to create an instance of an entity. I would like to manually set the GUID, but if I had the attribute that is the primary key to the DynamicEntity, I get following error.
Service could not process request
I am building a DynamicEntity, and setting the [entityname]id attribute causes the request to fail. It's moving data between two CRM instances, so if anyone knows of a better way to copy records between CRMs, that'd work too. Otherwise, I'd like the GUID to match across instances... as that's the point of a GUID.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
令人高兴的是，可以跨两个 CRM 实例执行此操作！ 一位同事知道解决方案，所以功劳确实属于他。
我的错误是创建了一个 UniqueIdentifierProperty 类型的属性。 实体的主键属性需要填写KeyProperty。 这两个属性几乎是相同的——属性类型是相同的，只是一个属性持有一个键，另一个持有一个唯一标识符。 Key/UniqueIdentifier 都保存 GUID。 （微软脑海中的又一天！）
准确地说，我正在做的是创建一个DynamicEntity，填充实体名称，并填充大部分属性。 PK 属性（您可以从元数据中确定）可以用 KeyProperty 填充。 我用 UniqueIdentifierProperty 填写它，CRM 拒绝了该属性并用一条不伦不类且无用的错误消息进行响应。
Happily, it IS possible to do this across two CRM instances! A co-worker knew the solution, so credit really belongs to him.
My mistake was creating a Property with type UniqueIdentifierProperty. The primary key attribute on an entity needs to be filled in with a KeyProperty. These two properties are nearly identical -- the Property types are, except that one holds a Key, the other a UniqueIdentifier. The Key/UniqueIdentifier both hold GUIDs. (Another day in the mind of Microsoft!)
Precisely, what I'm doing is creating a DynamicEntity, filling in the entity name, and filling in the majority of the attributes. The PK attribute (which you can determine from the metadata) can be filled in with a KeyProperty. I was filling it in with a UniqueIdentifierProperty, which CRM rejects and responds with a nondescript and unhelpful error message.
如果我过度简化了解决方案，我深表歉意，但为什么不在两个实例中添加一个自定义字段来作为其他实例 GUID 的镜像呢？
I apologize if I am over-simplifying the solution, but why not add a custom field in both instances that would be a mirror of the other instances guid?