Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, Power Apps, Power Automate, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
I have created one header table and i want it to have track of all changes like versioning on that header table.
what steps should i follow to create versioning for table.How does it work ?
Please have some light on this.
Have a great day.
Dear Experts please reply on this
Can you tell us more about your business requirement, please?
Have you consider using the database log?
Thanks for your reply.
I have header table.If some modification is done to track and i need to keep history so that i can get back old data through report like purch confirmation.
Can you please help me on this
It really depends on your exact requirement.
- You can use database log to track changes.
- You can use the date effective framework to create a new version if your data is changed (similar than what you see in LogisticsPostalAddress table)
- You can save a "posted" version of your data into another table, and if data is changed, post a new entry. The data in the other table(s) is blocked from editing. This is how purchase confirmation works, as well as invoices, packing slips etc. You can always see what data was used in old confirmations, invoices etc.
I still don't know anything about business requirements, therefore I can't say which technical solution would meet these requirements.
Regarding purchase orders, some historic data is stored in tables such as PurchTableHistory and PurchLineHistory - look into the standard application if you're interested in details (VersioniongPurchaseOrder.archiveCurrentVersion() might be a good starting point). Just don't forget that this isn't the only possible approach.
Thanks for your kind reply
My requirement is similar to have version to new table so that I can get later previous records
I need help on steps how version works and how to create version state to new table.
There is no magic in copying data to another table - you create a record, assign an ID, copy the data you want and save the record.
Unless you have additional business requirements...
I am asking any standard table except purchase one because they are using some maps there to insert.
I need simple standard table which is having some version so that i can check how that works
Just create a copy of your table. Then, in insert and update methods of your original table, call a method (which you need to develop) that creates a new record in the new table, copying field values from your original table record.
Also if you need a version number in the version table, create a numeric field for it, and increment it by one for every new record. The numbering should be separate for each unique in the original table. When you copy a new record (from insert method) the version nr will be 1. When you copy an updated record, the version number is 2, 3, 4 etc.
In the new table the unique index is the same than in your original table, + the version number field.
Is it clear now? If not, please let us know what is the difficult part for you.
Thank you nikaloas for your clear explanation.
I got it now.
Business Applications communities