Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

IT: Looking for analytic/report versioning best practices and tips

edited Aug 1, 2017 9:51PM in Reporting and Analytics for HCM 6 comments

Summary

I'm looking for advice and best practices on versioning reports, analytics, and dashboards in a repository.

Content

Hi everyone,

I'm looking for advice and best practices on versioning reports, analytics, and dashboards in a repository. The point of this exercise is being able to identify which version of a codebase is running on the BI system.

We have attempted the use of archiving. However, this seems risky because of the potential to lose historical work due to the issue found in this post - https://cloudcustomerconnect.oracle.com/posts/2380a6aa7b - It seems that with different releases, it is possible that your archive could become invalid and you would not be able to revert to a previous version as a result.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!