I had the feeling of it, dealing with different modules of BO last few years, I know how frustrated it could be. I didn’t do extensive vba though…
Thank you very much for your comments and help
Agree with the Step 1 a VBA macro, which will document the report when it is exported to the repository or manually by the developer if you trust them.
Step 2 I have a lot more problems.
Depending on the user settings and where they refresh the reports it may fail because of a VBA error. (Zabo is different from BO)
You will need a connection from every Client to write directly into your log database
How do you identify the report as being the right one (DEV or Production)
What happens if users make minor changes to the SQL/Report you may get
What happens when user use the “save as” function …
The Run from the query panel as you mention is one of the nastiest things in BO because it does not exist. We have created our own events to get around some of the limitations.
Dave,
Thanks again. The client wouldn’t like to have vba in their published reports, since they are distributing the report using InfoView and not confident that reports and vba will work in this environment…they are not using ZABO.
Since each report has it’s own code, I don’t see this as a problem. Part of the migration process (DEV to Prod) would involve changing the value of the “report ID”.
In the scenario Marina outlined, I was treating the users as Infoview users, and therefore neither of these would apply.
By revoking access to the query panel, you could avoid this.
Marina seemed to have a very specific case. The solution I outlined was just a suggestion, not a final product. 8) Obviously there are questions to be answered, but in her case, it seemed that since the users never create their own reports, and (in theory) would never make alterations to the standard reports, then something a bit more basic could be done.
By distributing the reports via Infoview, the concern that Klaus raised about connections is a moot point… since all the reports are run on the server, you can guarantee that there is a connection. And since you are on the server, you already have half of the solution… don’t write your own, just use what is already there!
Simply turn on the standard Webi auditing process. It will log which reports are opened and refreshed. By comparing this log to the report documentation that I suggested earlier, you can capture what you need. The Webi auditing does not capture class and object information for full client reports. But by setting up that information on your own, you should be able to get what you need.
And since you are using Infoview, you can guarantee that nobody is going to use the query panel.
Actually, I don’t think this is the case. I believe that you only get that level of detail for Webi reports, not full client reports refreshed under Webi. Also be aware that even for Webi reports you only get details about result objects, not condition objects.
Create a query in webi, and review the data collected in the audit tables. Create the same query in ZABO and see what you get. I don’t think you will see the same level of detail… unless they have improved the collection process since I last looked at it. What version of Webi / ZABO are you running?
You do not have to purchase Auditor. If you are using Webi / Infoview to distribute the reports, then you can simply turn on the Webi auditing feature. The data is logged to a database, where you can then do whatever you want with it.
Auditor - the “product” - is a pretty front-end that BusinessObjects has created to provide a reporting framework. The data is there if you want it.
Thanks, I do not have administrative rights to WEBI server to turn on this feature. I basically have no access to the server. I can only propose that to one who has “a power”.
Understood. 8) Just wanted to make sure that you did understand the option.
Also, since this discussion has wandered a bit from the VBA / SDK issues, I’m going to move it into the General Discussion forum. Folks that don’t view the SDK forum might have something worthwhile to contribute.
Yep I see 'em. Created a report and the application name is ‘BusinessObjects ZA’. Event type is 18 and event type name is ‘Object Name’. We’re 2.7.2 CSP 519.
Look in the Webi Admin guide. Ummm, about page 240? Or something like that. You can do a search for “audit” in the PDF and find it. They have table definitions and discuss the contents that are collected.
You can learn a lot reading this thread and others you can find doing a BOB search. You can also learn a lot just by looking at the universe and reports in the download area. I didn’t find the documentation too helpful .