Supply chain | Supply Chain Management, Commerce

Why are fields automatically created in my staging table when I create an Entity? Can I delete them?

(0) Share

Report

Posted on by ForeverLearning

I've created a custom table. When I created an entity from this table it also created a staging table for me. The staging table includes 4 fields that I didn't explicitly include.

When I build the solution, I received multiple errors on these fields indicating an extended data type does not exist. I see what the error is saying... it's pretty clear it's missing references.

I just don't have context as to why these fields are here in the first place... Is it ok for to delete these fields and just move on? Or are they important and should I map them to something? If so, what should I map them too? I tried looking for each one in the extended data type drop down (with and without 'DMF' prefix) and I was unable to find anything that matched by name.

This is a fresh install using app version 10.0.8 & platform version 32, we've made no changes to the environment up until this point. We also saw this in 10.0.7 as well.

I have the same question (0)

All responses (5)

Answers (0)

ForeverLearning 22 on at

Like (0)

Report

Also I looked over: docs.microsoft.com/.../create-a-custom-target-entity-for-the-data-import-export-framework-dixf-dmf

I am unable to select any of these (DMFDefinitionGroupName, DMFIsSelected, DMFExecutionId) for Extended data type for the fields. Could this be a product bug? This seems pretty big.

Was this reply helpful? Yes No
Suggested answer

ForeverLearning 22 on at

Like (0)

Report

Digging more I think I have found it... still would like to know from community about the context of this.

I added the package 'Application Foundation' to my package.

community.dynamics.com/.../can-we-reference-all-packages

Was this reply helpful? Yes No
Suggested answer

Rahul Mohta 21,032 on at

Like (0)

Report

in data entity, there are system fields which always gets added like execution Id, date.....

if you are using BYOD, then could the data in them populated and are needed for reference and change tracking purpose

Was this reply helpful? Yes No
Suggested answer

Navneeth Nagrajan 2,438 Super User 2025 Season 2 on at

Like (0)

Report

Hello Foreverlearning,

Just to add to the question, the four fields should exist in the staging table (Mandatory fields). All you need to do is Right Click on the Entity and update or regenerate the Staging table that is associated with the entity. In Data Management related activities, ExecutionID, TransferStatus, DefinitionGroupName and IsSelected are mandatory fields and very much required (especially while performing data imports into FO).

The fields that are added to the entity should be added to the staging table, by default. Ensure that you have the correct staging table associated with the entity.

Thanks,
Navneeth Nagrajan | Dynamics 365 Technical Consultant

Was this reply helpful? Yes No
Suggested answer

Martin Dráb 237,926 Most Valuable Professional on at

Like (0)

Report

These fields are necessary and you mustn't delete them.

For example, a single (import or export) job can be run multiple times and you must be able identify which data set belongs to which execution. And the same staging table may be used by several jobs. This is the purpose of ExecutionId. If such a field didn't exist, these things couldn't work.

TransferStatus is used for tracking the status (e.g. whether the record hasn't been imported yet, it was imported or the attempt of import failed).

And so on.

Was this reply helpful? Yes No