You cannot do it in Infoview. Instances are stored in the same folder where the original reports resides or some other destinations that are provided in Infoview. (Network, FTP etc.)
If you want to put few instances in Business Objects folder, then you can create SHORTCUTS and place these in the Business Objects folder.
We have sent BO Report output to a file location which was a virtual directory for IIS on another server. Then created a link to point to the directory (kind of low class solution, not very managable for many files). So we then took these files and wrote a java program to load them into specific folders in sharepoint for internal users. This solution allowed for a bit more organization of reports.
Hi
Did you manage to resolve this?
I need to send a file to another location on another server if I put \servername\drive$\directory
it fails.
It also turns my slashes around.
Do I need the full domain name of the server or is there something else I’m missing?
Hi SaraG,
We had a similar issue with sending reports to other servers and found the cause was that the ‘BO User’ did not have the correct permissions to write to the other server. We were able to confirm this by selecting a folder location on a server that everyone had read write access to and found that BO could successfully write them there. Also don’t worry that the slashes are reversed it has nothing to do with your issue
Hi - I am a functional user of business object. I am trying to schedule the report using File location. This means, I can provide any window server path and the system can post the report in the designated path ? If thats the case what should be the user name & password? thanks in advance.
When scheduling the report, specify a Windows domain user account and password. This will be used to connect to the file share. The specified user account must have permission to write to the location.
Leave the user name and password fields blank. BO will attempt to connect to the file share with the user account that the BO server is running as. By default, the server runs as the local system user, which can’t connect to network shares. So a domain account must be specified.
I recommend option #2 whenever possible. With option #1, if you change your password, you must re-schedule all reports that use it.
Don’t know if this is any use but I found this topic whilst trying to schedule to a folder within Launchpad.
My eventual solution was to create a shortcut to the report but the user did not have permissions to view (in testing). So I tested adding User permissions to that report. This succeeded and so I extended this to the Group they were a member of. This worked and now they can view the report and its instances.
(BOB member since 2011-01-15)
(BOB member since 2004-06-06)
(BOB member since 2005-08-22)