web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

DMF / BYOD - no records exported

(1) ShareShare
ReportReport
Posted on by 354

Hello,

I set up DMF for BYOD in D365. I followed all the required steps and have it working for three custom data entities just fine.

Now, I added two base data entities, Customers V3 and Vendors V2, which both have a few custom fields on the custTable/VendTable.

When I turn on change tracking on the entity page, change tracking is set to custom no matter what I choose. 

When I run the job, everything looks great and I'm told I exported 1000s of records. However, not a single record shows up in these

two tables in the BYOD.

I was looking at this link : https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/entity-change-track and was 

wondering if I need to create that method myself, but it is already present on the base data entity. We haven't changed any datasource

hierarchy, just added a few fields.

Any ideas or suggestions how to resolve this ?

Thanks for your help.

I have the same question (0)
  • Verified answer
    Rahul Mohta Profile Picture
    21,032 on at

    try disabling change tracking and then export

    if it is till does not then compare BYOD and D365FO entity data schema from data management tile - 'Confgure entity export to database' and then click on publish button and then select the entity and then use button 'compare source names'

  • Suggested answer
    Sergei Minozhenko Profile Picture
    23,093 on at

    Hi Frank,

    Do you see if the status for the export job is Ended (not Executing)? Also, double-check that you set up source correctly, maybe you are exporting data to the wrong BYOD (or source format is wrong in data project).

    If there is already added method defaultCTQuery on base entity, you don't need to create a new one. Also, you can always use "Primary table" (preferable option) and "All tables" options if you don't have defaultCTQuery created.

  • Suggested answer
    Frank Bruemmer Profile Picture
    354 on at

    Rahul,

    thanks for your response. I turned off change tracking and according to DMF, thousands of records have been exported. None of them made it to the database. Next thing, I checked the schema and I noticed that the corresponding fields for the four extended fields were missing. I clicked 'append schema' which was the only option available and that fixed the mapping for the extended fields. I ran the DMF job again and it still didn't work. I double-checked the mapping on the job and noticed that it wasn't correct. I went and recreated all the lines in my job, reselecting the entities and regenerating the mappings in the job. I turned change tracking back on where I turned it off before and then it worked.

    Conclusion : If there's custom fields, the entity/BYOD mapping (schema) needs to be regenerated - similar to regenerating the mapping on the 'Entities/Map Staging To Target' form - only that it is called 'append schema' in this case.

    Thank you so much for your help.

  • Thomas Treen Profile Picture
    on at

    Hi Frank,

    Test something simple as well like Customer Groups to the BYOD data source you setup. See if that will publish. I typically use that for a quick test, as it's a very simple entity.

    Thanks, Tom

  • Frank Bruemmer Profile Picture
    354 on at

    Sergei,

    thanks for your response. This wasn't a execution issue. Three out of five entities exported successfully.

    'Custom' was the only option available other than 'disable' for changing the change tracking, I assume because of the presence of custom fields in the data entity extension.

    Please see my response to Rahul's post which describes how I got this to work. Thanks for looking at this anyways.

  • Sergei Minozhenko Profile Picture
    23,093 on at

    Hi Frank,

    Yes, If you added new fields you need to perform at least 3 actions to make them visible in BYOD (in correct order)

    1. Regeneration mapping on the entity

    2. Publish missing fields to BYOD

    3. Re-add entity on a data project

    But if you don't do these steps right after the release, the export will still work. New field will not be published and exported to BYOD.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 660 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 549 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 307 User Group Leader

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans