Dynamics Community Forum Thread Details

DMF Import Validations

Hi all,

When using data management framework to import data to a data entity, is it possible to apply an all-or-none type of validation so that if any of the records are invalid then you reject all of the records? My users would prefer if they attempt to import 100 records from an excel file using DMF, if one record has a validation error then none of the records should be created. I was reading the documentation about data entity validations here:

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/validations-defaults-unmapped-fields

From this, it appears we just have field and record level validations and I didn't see any good examples of how to apply a transaction scope to all of the records being imported so that I could accept or reject all of them as a set. Is there any example in the system that creates a transaction scope around the process that copies the data to the target tables so that I can roll back all of the rows if any one of them are not valid? Or does this type of design go against the spirit or concept of data entities in D365? If we cannot do it at the time of writing to the target tables, is it possible to do this type of validation on the staging tables before any records begin writing to the target? I am struggling to find good examples of either of these approaches and from my experience it seems the staging is getting written to at the same time as the target records. Any examples or direction on a validation like this would be greatly appreciated! Or confirmation that this is not a good design pattern and that I need to adjust my user's expectations on this is also appreciated!

Categories:

Dynamics 365 general

Quick Links