I have a requirement to be able to "version" data in the Ax database.
Example:
We have a set of tables related to contract administration, which
define our legal obligations to our clients. Changes to CERTAIN
fields must result in a new "version" of related contract records
being saved while keeping the old "version" available for inquiries.
Possible solutions so far:
1. Maintain a "current version" and "previous version" set of
tables. Move data from "current version" to "previous version" to
archive when an amendment is made.
"Previous version" table schema is identical to "current version"
except from version indicator which forms part of the primary key
2. Create a primary key consisting of the version id with a version
status indicator(allow only one active version).
Any ideas will be most welcome.
Regards,
Christoph
SPONSORED LINKS
| Computer part | Programming languages | Microsoft axapta |
| Support exchange |
YAHOO! GROUPS LINKS
- Visit your group "development-axapta" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
