Archiving incident records
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-24-2018 07:10 AM
I have a few questions with regard archiving
I am unsure from the documentation what the archived record will look like in relation to the original record, is there any relationship in the names? is it a one to one relationship or does one archived record cover a date range?
How is the naming convention and how easy is it to (say) restore all incidents between January and March 2015 if we were required by audit?
Can I export migrated data to another environment by exporting the and importing the files? Are there any known issues around this?
- Labels:
-
Best Practices
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-25-2018 12:43 AM
Ouch, sounds like a messy job!
I think if you're exporting archived records to be imported into an archive table that would probably be ok. Really it depends on what data you have on your incident form, what is stored on referenced tables and what is required for audit. I'm not sure how detailed you can be in archive rules when archiving related records but i can't imagine the archive process would take longer than the lengthy reconciliation you will otherwise have to do.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-24-2018 07:39 AM
I like what David has Suggested.
Archive 1 record on a dev instance and try everything you want on it(Like exporting, related records etc) and if it suits you and the business go for it.