Notifications
Announcements
No record found.
HI We are using DMF for mass data migration from CE to F&O, but the import job fails and there is no data in staging table and no error at all. We know it's data issue but it's hard to detect when the data set is so huge.
Is there anyway I can customize DMF so I can get error out when it's bulk copy the source to staging?
Thanks very much!
Hi,
If there is no log in staging table, kindly check in view execution log, from there you will get info log, staging log details and view error files.
Hi Yvone,
I don't think you can get this error out. Could you please tell us which entity you are using for import? Is it OOB or customized?
Hi Yvonne,
If you don't see data in staging, you need to check the execution log and staging log details.
If data entities fail (shown with a red x or yellow triangle icon on the data entity tile) after you click Import, and View staging data shows no data, go back to the Execution summary page. Go to View execution log, select the data entity, and review the Log text, Staging log details, and Infolog for more information. Staging log details will display Error column (field) details and Log description will describe errors in detail.
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/data-entities-data-packages#import-process-troubleshooting
Have you considered to chop data sets into smaller pieces? Sometimes is easier to identify the issue.
Hi Yvonne
I don't think you need customizations, we had a similar issue when finding DMF errors because data volume is high. the main issue is we cannot view errors as a list & need to browse through one at a time, there are three tables you can look in to,
1.DMFStagingValidationLog
2.DMFDefinitionGroupExecutionHistory
3.DMFDefinitionGroupExecution
Just open using Table Browser and Filter Data Project or Entity Name as relevant.
Hope this will help,
Amith Prasanna
You have to go with one of the workarounds provided above. The source to staging process is handled by a package executed by SSIS. So, in fact the SSIS job fails in case there is a mismatch in data format, missing mandatory field or duplicate record.
There is no way to customize the SSIS package or behavior.
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.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Martin Dráb 551 Most Valuable Professional
André Arnaud de Cal... 450 Super User 2025 Season 2
BillurSamdancioglu 278 Most Valuable Professional