I hope I am on the correct Forum page to ask this question again…
We are currently using BOXI 3.1 Deski for our client reporting. We use VBA macros extensiviey to burst out the reports to excel. We have few VBA macros running for client specific reporting functionalities other than standard scheduling and publishing provided by BOXI.
We currently reference Business Objects Library 12.0 DLL in the VBA macro to accomplish this.
I am interested to know if Business Object Library DLLs will still be available in BOXI 4.0 for running macros when we have migrated to BO XI4.0?
Currently we have an external Excel spreadsheet with macros in it. These VBA macros does various jobs for us other than Scheduling and Publishing.
When we run this VBA macro from Excel spreadsheet, it creates a Business Object Application instance on 3.1 version and works on the DESKI Report accordingly to burst/copy/move to functionalities…
I will look into this more on your advise to use JAVA… I have no idea how to incorporate this at the moment, I probably may ask more questions in this forum if I don’t have any clues…
JOSEPHINE: Yes, I agree that VB can offer some cool ways to do stuff that is not implemented by default in Xi, but as Marek said, you will need to look forward and see how you could convert your current functionality to something that works without the VB code.
It seems the Excel files are the one that triggers the report to create a BO sessions, run the report and burst. Thinking you could use a different approach.
Yes, perhaps stating your current workflow will help members of the forum to post valid suggestions for your business issue.
I will see how far it is possible for us to use XI 4.0 capability for our needs which VBA is performing at the moment.
I will soon update in the forum what we are doing in our VBA, so can someone help me.
I will be back…
There are .NET libs available in 4.0, but not for the ReportEngine. If you need to use more advanced features of Webi, then you may have to look at the Java SDK.
We had a .NET app that was going against the local .NET SDK and also the Web Services SDK. Because of the issues in the initial BO implementation, we actually decided to re-write in Java, then created a way to communicate between the Java and .NET processes. This gave us the FULL power of the SDK, so we are prepared for the future.
You could also look at third party bursting tools like InfoBurst.
You can consider using BO Live Office to get data in to Xcel and then your macros. I guess between Live Office 4. x and your custom excel macros, you can get same funcationality you are having now in BO 3.x.