I am using the BO XI 3.1 version 12.1.0.882 and am having problems using a web intelligence document to provide the recipients list, every time I select my report, it says “Invalid report! Please choose another report” after I select the datasource name for the document.
I have purged the data from the webi report, and also set the report to refresh on open.
I tried to make an identical report using the desktop intelligence tool, and uploading this and using this as the dynamic recipients data source, then this actually works, and it is using the same SQL resultset.
Does anyone know why I am having problems using a web intelligence document as the dynamic recipients source, when I can use a deski documument without a problem? I think that this functionality used to work for people; people have made publications in the past in my company using one report and another webi report for the dynamic recipients, but now when they try to make a publication using those same two reports, they get the invalid report error message.
Is there a way to get a more detailed expansion of what the “invalid reports” error message means?
The server hasn’t been patched or upgraded in a long time. I’ll try to find out the exact date, but I don’t think it will have been patched in the last year or more.
The existing publications still work, it is just the new ones cannot be created with dynamic recipients, even using those same reports, because when I try to choose the query after choosing the report, then it gives the message about it being an invalid report. I attached a screenshot of where the error is, if it helps any.
I did see this post, but it didn’t solve my problem I’m afraid.
This is upon first creation of the publication, not the modifying/scheduling of the publication, as the other post was. Even so, If I save the publication and then try to clear the publication completely before reopening it and reassigning the report, then I still get the aforementioned error message.
Asking around, the last publication we made was around August 2011. The last time we updated the server was around March 2011. We won’t have installed any hotfixes/patches to the BO server since August 2011.
Hi,
I have faced the same problem.
I have got rid of the problem by creating a new report and adding the new report with different name or copy the existing working report as dynamic recipient from other Publication and modify.
May be it is not the optimum solution, but it might be work around.
May be it is registering by “CUID” and path when it encounters the first error
Hope it helps.
Thanks,
Ratna
That note basically says that you should put a limit on the burstmap. In properties, you should set the maximum retrieved rows to a value greater than the number of lines you’re expecting.
It doesn’t work for me though.
What does work however, is to restart the BO server – until such time, you can use a DeskI report as your burstmap.
(BOB member since 2005-01-06)
(BOB member since 2005-01-06)