Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I would like to remove historical data from all Axapta3.0-tables before 2014.
Does one of you have experience with this?
Maybe someone has suggestions to get not to many issues at the customer?
Thx. in advance.
There is no tool for this. Note that deleting records in certain tables like LedgerTrans and InventTrans is not advisable. Why do you want to clean up the data?
Communication in Dutch is also possible I see but let's do it in English.
Thx. for your reply. But it has to do with the recid's which started again.
And we have only a gap of 1.000.000 and that will be consumed within 10 days.
Maybe you have an idea?
Most tables don't create the creation date, so how do you intend to find out if records were created before or after 2014? It's impossible to get this information from the data itself, because it's simply not there, so you either have to introduce some other source of information (such as backups from 2014), or you have to change your requirements (restrict it just a few tables or use different conditions).
Consider the Intelligent Data Management Framework (IDMF) - it can be used archiving and purging data and it supports, or used to support, Axapta 3.0.
It's a pity that you haven't upgraded your AX at least once in the past ten years; newer version doesn't have such a limit of record IDs.
Note that when you need to purge data from the InventTrans table, it is not supported. Some functionality does actually require to have all InventTrans records available. One of those features is the consistency check which is able to rebuild the InventSum table when there is an issue.
Like Martin said, later versions do support 64-bit integers where this limitation of record IDs are solved.
There were some issues in the past with negative record IDs. Probably you can try to force the system to use negative record IDs.
In the meantime consider upgrading to a recent and also supported environment.
PS Dutch communication on this forum is not allowed as it is a English lingual forum.
Hello Andre and Martin,
Both thanks for the given answers. The negative recid's where already used.
Maybe IDMF can help us. I am not sure if it also available for Axapta3.0
In addition, I have already worked in AX 3.0 with negative Recid without issue.
Also from a performance point of view, consider to check eventually missing indexes through Sql Server Profiler.
Archiving is not really an option for high frequency transactional tables unfortunately.
Have you considered going completely fresh? Keep a copy of your current environment / database somewhere for historical and legal purposes, bring over master data to a clean install, do your opening balances for the ledger and punch in the open orders and whatever else you need to transfer over to have a functioning system.
Thx. for this suggestion. My idea is this the best route.
There is no reference between the original answer and your reply. Can you mark the answer which helped you now? Then the question will get the status answered also.
Business Applications communities