2017 Jan 13 10:19 AM - edited 2024 Feb 03 6:36 PM
We have an issue with report distribution using the BOBJ broadcast feature.
We have 2 reports.
Both reports share the same logic for identifying people and the same prompt parameters.
We schedule the distribution list refresh to run 5 minutes before the broadcast report, to ensure an up to date list.
The issue is that the broadcast report does not see the instance of the distribution report that has just run, but instead uses the cached results from when the report was saved. So instead of sending to 2 people, it will send to 5 people (2 with issues, and 3 blank reports).
I have tried purging the distribution list and saving, but that results in no distributions. I have tried setting the distribution list to refresh when run, this doesn’t work either.
So the net results is that the distribution function is not correct as the target audience differs. See attached PNG exampledistributiondata.png
I am using Publication for report 2. In the publication, I use the results of report 1 to determine the dynamic recipients.
1 run report 1 (on schedule) 10 minutes before the publication runs, so that the distribution list is up to date.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes this is using normal BO Scheduling
1. Report 1 (Distribution list) is scheduled at 9:45 to prepare the list
2. Broadcast 1 (Quality report) is scheduled at 10:00, and this uses the distribution list created in report 1.
the problem lies with the broadcast, it doesn't use the results of the latest run of report 1, instead it uses the values from when report 1 was "saved".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
73 | |
10 | |
9 | |
8 | |
8 | |
6 | |
6 | |
6 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.