Best Practices question

My group is starting to create Crystal Reports on top of BW queries. We have a report right now that is using a query. That query is also used by Bex Analyzer users. The Bex users requested some changes to the query. Once those changes were transported to production we found that the Crystal Report was now broken. I refreshed the data source in the report and was able to get the report working again but my user had to go in and recreate all of his scheduled instances.

My question to everyone is are there any “Best Practices” for this type of senario? Should we take a Universe approach for the Crystal Reports or should we just create a new version of the query for reporting?

Any advice would be greatly appreciated.


twetterau (BOB member since 2010-09-16)

[Moderator Note: Moving to Crystal Reports - Jansi]


Jansi :india: (BOB member since 2008-05-12)

I would create a new version just for reporting. That way changes to existing queries for non-reporting purposes won’t affect your reports. The drawback to this is that if the logic for something significant changes, you’ll need to update the relevant reporting queries in addition to the non-reporting queries.

-Dell


hilfy :us: (BOB member since 2007-04-16)