Dynamics crm 动态API-在创建时关联多个实体
是否可以在API Create调用上关联实体,其中关系为ManyToManyRelationship,如下所示Dynamics crm 动态API-在创建时关联多个实体,dynamics-crm,microsoft-dynamics,dynamics-crm-online,dynamics-crm-365,dynamics-crm-webapi,Dynamics Crm,Microsoft Dynamics,Dynamics Crm Online,Dynamics Crm 365,Dynamics Crm Webapi,是否可以在API Create调用上关联实体,其中关系为ManyToManyRelationship,如下所示 { "SchemaName": "testscheduleid_testid", "Entity1LogicalName": "testschedule", "Entity2LogicalName": "test", "IntersectEn
{
"SchemaName": "testscheduleid_testid",
"Entity1LogicalName": "testschedule",
"Entity2LogicalName": "test",
"IntersectEntityName": "testschedule_test",
"Entity1IntersectAttribute": "testscheduleid",
"Entity2IntersectAttribute": "testid",
}
上的示例仅显示一个omany
Or/tests(00000000-0000-0000-0000-000000000002)/testschedules/$ref是通过REST API的唯一方法Web API只有两种类型的关系的概念:
- 单值
- 收藏价值
POST [Organization URI]/api/data/v9.0/accounts?$select=name&$expand=primarycontactid($select=fullname),Account_Tasks($select=subject) HTTP/1.1
Content-Type: application/json; charset=utf-8
OData-MaxVersion: 4.0
OData-Version: 4.0
Accept: application/json
Prefer: return=representation
{
"name": "Sample Account",
"primarycontactid@odata.bind": "/contacts(00000000-0000-0000-0000-000000000001)",
"Account_Tasks@odata.bind": [
"/tasks(00000000-0000-0000-0000-000000000002)",
"/tasks(00000000-0000-0000-0000-000000000003)"
]
}
虽然这是一对多关系,但使用表示N:N关系的正确集合值导航属性,其工作方式应该相同
忽略相交实体。
在$metadata中查找正确的集合值导航属性我创建了一个github问题-让我们看看: