18

Sometimes we need to bulk delete records and using data management would be a very convenient utility for this.  Another application I've worked with had an additional column that could be added to the import file (e.g. CSV, etc) that was called DELETE.  If the column had a certain value (e.g. !DELETE!), then it was a cue to the import utility that this line/record should be deleted.  Simple and very effective. :-)

Category: Data Management
STATUS DETAILS
Declined
Ideas Administrator

Thank you for sharing this scenario. As of now, we are focussing on working on next gen import/export capability using data feeds. Also, when we work on archival and purging, deletion of mass data will be addressed. 

Comments

D

Year 2022. This is still a missing feature.

Category: Data Management

D

I know this is from 2017 but current solution in case this option to delete records is never implemented:

Workaround: "Truncate entity data" truncates all existing data and imports the data that is in the file. File cannot be empty. Keep only one record in the file and choose option "Truncate entity data" during import. In this case, it will truncate all existing data and import only one record from file. Then just delete this one record manually from UI.

https://community.dynamics.com/ax/f/33/t/259071

Category: Data Management

D

I was reminded today of the need for the ability to DELETE records via Data Management. :-)

Category: Data Management

D

Add line with new button would be also good.

Category: Data Management

D

 


Yes, I feel that this is very necessary.


I can provide an example where this delete functionality is required in data management.


Scenario : We have MDM (Master Data Management) in AX 2012 R3 CU 8 environment where the data will be replicated from a single master legal entity to slave legal entities. As per MDM, if record(s) is/are inserted/updated in master legal entity, then the same record(s) will be inserted/updated in slave legal entities. But in case any record is deleted from master, then the same will be not be deleted in slave legal entities even after the synchronization from master to slave legal entities. The AX 2012 Data Import/Export Framework handles the import and export of updated records between each AX 2012 instance and SQL MDS by using Data Import/Export Framework entities in MDM. Since DIXF can not handle the deletion operation, the data inconsistency exists between the legal entities.


I hope MS understands this and implements the deletion operation in data management process in new release.


Thanks David Simon for bringing up this idea :)

Category: Data Management