Reporting on Archived Tables

[Anurag Tripathi]

I am going to start Archiving on my instance and the biggest question i am facing is what are the options for reporting on archived data as users will want to see their data.

So i just what to know what others have done and what are the best ways i can choose from.

[pneuvil1]

So for can you use the standard reporting interface to report on archived data?

And is the presentation of the archive data in the reporting interface the same as non-archived data? Or is it one flat table?

[Michael Fry1]

You can report on the archive tables or access via list view and use filters to get to data you want. Initially the archive form contained all fields, but we made the form view similar to our regular views.

[daveslater]

I'm facing the same problem. 

We're about to archive off our old CMDB data in a big project that will see brand new classes and relationships etc.

The Configuration Items listed in other ITSM records (incidents, etc) are still there after archiving, but cannot be reported on via the Incident table without resorting to keywords which skews the data. 

Frustratingly, I can GlideQuery the archived CI sys_id looking at the normal cmdb_ci field and get the correct results. Just seems like the reporting engine is hiding it from us.

[Kim Sullivan]

I'm interested in this also.  I want to archive but need the total counts to show up in reports. Anyone have any experience with this?