Composite entities dataset failing error

[eveporras23]

When trying to upload composite entity packages, the package doesn't run and failed on AX with the next error:
A DataTable named 'PurchaseOrderV2Entity' already belongs to this DataSet.
'0' 'Purchase orders composite V2' record(s) inserted in staging.

Manually from dynamics 365 environment import data management we don't get that error.

[shankarmaha]

I am also getting the same error when trying to upload BankStatement. Manual import is working fine. Please let me know if you are able to fix this.

[shankarmaha]

@eporras23 , did you manage to get this issue resolved?

[eveporras23]

@shankarmaha no yet

[srpraveenkumar]

@eporras23 and @shankarmaha - Are you using the Recurring integrations API or the On-Demand Data Batch APIs ?

[eveporras23]

@srpraveenkumar the PackageDataHandler app

[srpraveenkumar]

This looks like a bug, kindly contact the support team.

[amorimdub]

@shankarmaha I'm getting the same error on BankStatement. Did you solve it?

[ptornich]

@eporras23 do you managed to solve this?

[maveloso]

Anyone manage to find root cause on this or solution?

[Edi-38]

I've got the same problem, and a resolution for this problem is really urgent, as we have a customer where this functionality is critical for going LIVE.
Exporting composite entities is no problem, but importing results in the error that the composite entity already belongs to the dataset.

When will there be a fix for this problem?

[Sunil-Garg]

Hi all-- we are looking into this issue as we speak. Apologies for not replying sooner. It will be great if we can all collaborate on Yammer's data management group which is more active and current. Thanks.

[RomanEder]

Following up in Yammer:
https://www.yammer.com/dynamicsaxfeedbackprograms/threads/1147343116