这是关于CDS多态查询(如客户和所有者)的ADF限制. 对此赞ADF想法

This is the ADF limitation with respect to CDS polymorphic lookups like Customer and Owner. Upvote this ADF idea

解决方法是使用两个临时源查找字段(如果是所有者，则是所有者团队和用户，如果是客户，则是客户和联系人)，并在MS Flow中使用并行分支来解决此问题. 了解更多，您也可以下载Flow示例以供使用.

Workaround is to use two temporary source lookup fields (owner team and user in case of owner, account and contact in case of customer) and with parallel branch in a MS Flow to solve this issue. Read more, also you can download the Flow sample to use.

• 首先，在要将客户查询数据导入到实体中的实体上分别创建两个临时查询字段，分别到客户实体和联系人实体
• 然后，在ADF管道流程中，您需要将客户"和联系人"字段的GUID值映射到上面创建的相应查找字段.最简单的方法是在源数据集中有两列-一列包含要映射的客户GUID，另一列包含Contact.
• 然后，最后，您可以将Microsoft Flow组合在一起，然后执行从临时字段到客户"查找字段的适当映射.首先，定义何时创建受影响的实体记录(在本例中为Contact)的触发点，并添加一些并行分支以检查这两个临时查找字段中的任何一个值

• First, create two temporary lookup fields on the entity that you wish to import Customer lookup data into it, to both the Account and Contact entities respectively
• Within your ADF pipeline flow, you will then need to map the GUID values for your Account and Contact fields to the respective lookup fields created above. The simplest way of doing this is to have two separate columns within your source dataset – one containing Account GUID’s to map and the other, Contact.
• Then, finally, you can put together a Microsoft Flow that then performs the appropriate mapping from the temporary fields to the Customer lookup field. First, define the trigger point for when your affected Entity record is created (in this case, Contact) and add on some parallel branches to check for values in either of these two temporary lookup fields

• 然后，如果满足以下任一条件，则设置更新记录任务以执行单个字段更新，如下所示(如果ADF帐户查找字段中包含数据)

• Then, if either of these conditions is hit, set up an Update record task to perform a single field update, as indicated below if the ADF Account Lookup field has data within it