CRM 2011 - 使用案例表单上的联系数据
我安装了 CRM 2011，看看是否可以根据我们的业务定制它。我们进行维修，我希望能够预订联系人（客户），然后预订案例，并将客户编号和地址打印在案例表格上。我能找到的都是与案例相关的字段，而不是与客户相关的字段，我知道如何选择它们吗？
I've installed CRM 2011 to see if I can tailor it to our business. We do repairs, I want to be able to book in a contact (client) and then a case and have the clients number and address print on the case form. All I can find are fields relevant to the case and not client, any idea on how I can select them?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
要将联系人中的字段获取到案例表单，您可以 -
在案例表单上为要从联系人移植的字段创建冗余字段，然后编辑从联系人到案例的关系映射以进行映射这些字段到案例。
创建一个加载联系人数据的 Web 应用程序，然后将其添加到案例表单上的 iframe 中。使 Web 应用程序接受 URL 查询字符串中的案例 ID，以便可以查找相关联系人并在 Web 应用程序中加载其详细信息。
将 JScript（或 2011 年的 HTML 资源）添加到案例表单以动态加载联系人值。您必须使用 SOAP XML（或 2011 年的 REST 端点）消息从 CRM 服务中提取数据，然后将其注入到 CRM 案例表单的 DOM 中。
选项 1 是最快的解决方案，但不是实时的（仅在首次创建案例时出现，并且必须与创建时的联系人相关。选项 1 还添加了一些数据库冗余。
选项 2 是最受支持的实时解决方案，但也 选项 3 比选项 2更
容易，但未来版本可能不支持任何 DOM 注入。
要
使用映射选项，请转到“设置”>“自定义”。展开左侧导航中的案例项。然后单击 N:1 关系并打开关系“incident_customer_contacts”。此关系将联系人与其案例连接起来。
在关系窗口中，单击左侧导航中的“映射”。这控制创建案例时从案例映射哪些字段。
单击新建并从左侧选择要映射到右侧案例的联系人字段。对要映射的每个字段重复此操作。请注意，这些字段必须是相同的类型，如果它们是选项集，则它们的每个选项都必须具有相同的基础整数值。
现在，当您从联系人创建新案例（或在创建过程中设置联系人）时，字段应映射到案例上。
To get fields from the contact onto the case form you could -
Create redundant fields on the case form for the fields that you want to port over from the contact, and then edit the mappings of the relationship from Contact to Case to map those fields to the case.
Create a web application that loads contact data and then add it to an iframe on the case form. Make it so that the web application accepts the case id in the query string of the URL so that it can look up the related contact and load its details within the web app.
Add JScript (or HTML resource in 2011) to the case form to load the contact values on the fly. You will have to use SOAP XML (or REST endpoints in 2011) messages to pull the data from the CRM service and then can inject it into the CRM case form's DOM.
Option 1 is the quickest solution but will not be realtime (only comes over when the case is first created and must be related to the contact on creation. Option 1 also adds some database redundancy.
Option 2 is the most supported realtime solution, but also requires the most work.
Option 3 is easier than option 2, but any DOM injection will likely not be supported for future releases.
EDIT
To use the mapping option, go to Settings > Customization > "Customize the System". Expand the Case item in the left hand navigation. Then click on N:1 relationships and open the relationship "incident_customer_contacts". This relationship connects the contact to its cases.
On the relationship window click on "Mappings" in the left hand navigation. This controls what fields are mapped from the case when it is created.
Click new and select the contact field from the left that you want to map to the case on the right. Repeat this for each field that you want mapped. Note that the fields need to be the same types, and if they are option sets, they will have to have the same underlying integer values for each of their options.
Now when you create a new case from a contact (or set the contact during the create), the fields should map onto the case.
鉴于 Craig 提到他正在使用 CRM 2011，我想澄清一下，对于 Cole 建议的选项 3，您还可以针对组织服务使用 SOAP Xml，或者仅使用 REST 端点，两者都将受到支持。只要您利用 CRM 的 Xrm.Page 对象在表单上显示数据并且不执行任何其他 DOM 操作，您就应该得到完全支持。
另一个选项，我们称之为“选项 2b”，是将要加载的数据的字段添加到表单中，然后添加一个注册到案例实体检索的插件，该插件将动态填充这些字段你。除了此时表单上的字段之外没有冗余。
如果可能的话，我个人会推荐选项 2b，因为将数据加载到表单时不会有任何延迟，并且它提供了最小的数据冗余、最少的服务调用和最少的额外自定义。
Seeing as how Craig mentioned he's using CRM 2011, I felt I'd clarify that for Option 3 of Cole's suggestion, you can also use SOAP Xml against the Organization Service, or just use the REST endpoint and both will be supported. So long as you utilize CRM's Xrm.Page object to display the data on the form and don't do any other DOM manipulation, you should be fully supported.
Another Option, "Option 2b" we'll call it would be to add fields to the form for the data you want to be loaded, then add a plugin registered to the Retrieve of the case entity that would populate those fields on the fly for you. No redundancy other than the fields on the form at that point.
I would personally recommend Option 2b if possible because there will not be any lag in loading the data onto the form, and it provides for minimal data redundancy, minimal service calls, and the least amount of additional customizations.
我的选择很简单。我们所做的就是使用对话框创建案例，并且在对话框字段中您可以动态获取联系方式详细信息。在创建新案例时的表单末尾，使用此动态值以案例表单提交。
有时，客户告诉我们电话号码自上次以来已更改，此方法使您可以选择动态更改客户的详细信息并同时在联系人实体和案例实体中提交。
My option is a lot easy one. All we are doing is using Dialog to create cases and in the dialog fields you can get contact detail dynamically. At the end of the form when you create new case, use this dynamic values to submit in Case form.
We get times when customer tell us that the phone number is changed since last time and this method gives you option to change customer's details on the fly and submit both in Contact Entity and Case entity at the same time.