Is there a way to exclude reports (global and personal) from an application package? We are trying to formalize our change management practices, but were dismayed to hear that reports will be overlaid along with the application settings. We can't have our users' reports being overwritten with old versions from weeks or months prior.
Archer 5.3 P2
We learned the hard way about personal reports (version 5.4) that it depends. If they are new since the last time that you copied down the database to your development environment, there is no problem. However, if they were created before you took your last copy of PROD into DEV, the report ID exists and will overwrite the most recent version of the report in PROD with the version that existed at the time of the DB copy. Does that make sense?
If you have access to run scripts against the non-Production instance databases, reach out to support as they should be able to provide you a script that can remove all reports (both personal and global) from those environments. We have taken the approach of not having any reports in our lower environments, to prevent the issues you describe.
A good practice before any existing application development is done is to package back the application from PROD down through the other environments. Often, Report Admins can modify Global Reports in Production because that's where the real data is. This can cause a problem when you package the application to production when the Global Report hasn't been changed in Test or Dev. I've made it a habit to package back an application from Prod to the other instances to reduce the risk of overwriting a Global Report in Prod.