We have a scenario in which we need to schedule a Webi Report for 170 user groups. The values for prompts varies for all users. We are ending up with creating 170 copies of report.
[list][:4bade26ee0]The easiest way (scheduling-wise), is to create a table in the datamart that contains each user’s BO user name and the value of the prompt. Then join this table in using a filter on @variable(“BOuSER”). This is row-level security. You can then schedule the report using the “Schedule on behalf of” function for the entire group – each report will run once for each user, and apply the appropriate condition
[:4bade26ee0]Set up a Publication, using a separate report that contains each user and the appropriate prompt value as the source for the values
[*:4bade26ee0]Define the values in Profiles, and set up a publication based on that profile.[/list]
Not a problem Joe. Whatever you suggested it benefited me.
But I am very sorry for troubling you again.
I also saw your suggestions in below link for which we also have requirement:
Instead of [Fund #] we have different object called “Group Name Key”. It works for single value. But is Group name key has multiple values it throws below error:
2013-08-31 10:58:17,125 ERROR [pool-4-thread-15] BusinessObjects_PublicationAdminErrorLog_Instance_941404 - [Publication ID # 941404] - An exception was caught while doing dyanmic recipient resolution. (FBE60304) 2013-08-31 10:58:17,128 ERROR [pool-4-thread-15] BusinessObjects_PublicationAdminErrorLog_Instance_941404 - [Publication ID # 941404] - An exception was caught while scheduling the publication. (FBE60203) [0 recipients processed.]
It would be really a great help if you can resolve our problem.
That’s a generic error – it could be one of a number of different causes. If you search here for FBE60304, you’ll find some suggestions. The one that worked for me was to make sure that the report containing the recipients was set to refresh on open.
Looks to me that you have not set Unix to be able to write to a windows drive. You need to mount the drive using a Unix app called Samba as far as I’m aware.