Hi all,
We are working on integrating an OMS with Dynamics 365 SCM and are trying to create Return Orders using a custom composite data entity.
Setup:
We have created:
- Custom header entity:
OmsReturnOrderHeaderV1Entity - Custom line entity:
OmsReturnOrderLineV1Entity - Custom composite entity:
OmsReturnOrderCompositeV1Entity
These are based on:
ReturnOrderHeaderV2EntityReturnOrderLineV2Entity
We duplicated the standard entities and adjusted staging tables, relations, and composite structure. We have added RowId and ParentRowId in new entities, since the standard entities do not seem to be built for composite usage due to these missing fields.
Current Status:
- Export using the composite entity works fine ✅
Issue:
During import execution, we get the following error in Execution log:
“Number sequence is not set”
ReturnOrderNumber is passed and also without ReturnOrderNumber (set auto-generate in Mapping).Question:
Has anyone faced a similar issue when duplicating standard entities and creating new composite entity to use in DMF?
Specifically:
- Is there any additional logic required to trigger number sequence assignment in custom data entities?
- Are there known limitations or best practices when duplicating entities like
ReturnOrderHeaderV2Entityfor composite usage? - Could this be due to missing standard framework calls during DMF processing?
Any guidance would be greatly appreciated.
Thanks in advance!

Report
All responses (
Answers (