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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

DMF Import – How to Prevent Partial Success and Enforce All-or-Nothing Processing?

(0) ShareShare
ReportReport
Posted on by 1,572
Hi All,
 
We have a requirement where data is imported into a custom table in D365 F&O using a DMF project triggered from Azure Data Factory (ADF).
The issue is that when some records fail validation, the DMF execution status becomes Partially Succeeded. For example, if a file contains 36 records and 3 records fail, the remaining 33 records are successfully imported into both the staging table and the target custom table.
 
In our scenario, the combination of:
FileName (from the CSV file)
LineNumber (auto-generated by DMF)
is used as the entity key.
 
The ADF team would prefer an all-success or all-fail approach. Their current plan is to treat any DMF execution status other than Succeeded as an error and trigger an email notification.
 
However, from the D365 F&O side, we would like to know whether there is any way to prevent partial processing and ensure that:
Either all records are imported successfully, or
No records are committed to the target table if any record fails.
 
Has anyone implemented a similar requirement? Are there any standard DMF settings, customizations, staging validation approaches, or transaction handling techniques that can help achieve this behavior?
 
Any suggestions or best practices would be greatly appreciated.
 
Thanks and Regards,
Raj D. Borad
Categories:
I have the same question (0)
  • Suggested answer
    André Arnaud de Calavon Profile Picture
    305,265 Super User 2026 Season 1 on at
    Hi Raj,
     
    As per design, DMF is not able to roll back the changes in case of an error. You requirement can be solved with a custom import job or another data management tool. You can also consider importing data in another staging table and then use a periodic job that moves the data from your staging to the target. Then you can also control if an abort command should be called. 
     
    Note that it is not recommended trying to change the coding of DMF itself using extensions.
  • Deepak Agarwal Profile Picture
    9,032 on at
    As its a custom entity, and system doesnt provide this out of the box, you can add customization within your data entity and dont need to touch DMF framework itself. 
     
     

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

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

#1
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 591

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 550 Super User 2026 Season 1

#3
Abhilash Warrier Profile Picture

Abhilash Warrier 543 Super User 2026 Season 1

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans