Comments on: Understanding and Suppressing the Report Message “No data to retrieve” http://www.businessobjectstips.com/tips/web-intelligence/understanding-and-suppressing-the-report-message-no-data-to-retrieve/ Business Objects tips, tricks, articles, blog, guides... Mon, 06 Sep 2010 16:52:46 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Marc http://www.businessobjectstips.com/tips/web-intelligence/understanding-and-suppressing-the-report-message-no-data-to-retrieve/comment-page-1/#comment-992 Marc Fri, 06 Aug 2010 14:27:16 +0000 http://www.businessobjectstips.com/?p=570#comment-992 Well I do not mind getting a message, but for my end users I would like to just change the contents so that it is less confusing. The message "No date to retrieve"/"there is no data . . . ." gives the idea that the data warehouse is empty. It's a too technical message. It's like your computer giving a message "Partnr 7231-A2 is above 70 degrees Fahrenheit". If the message would end with "but this is OK" it would not give the problem-feeling. Further my users do not know the query names, and they will have the feeling there's something going terribly wrong. You could start by naming your queries better. "No data to retrieve in FIN_TRANSACTIONS" is much clearer than "No data to retrieve in Query4". In my opinion it would better to have this message only in the editing mode for a report. Thus the error appears to the one that can deal with it. I personally find the union a horrible workaround, for every change implies changing two queries. A dummy line in your data is the other way. But the base problem is that BO gives no choice in suppressing it for the end user. Well I do not mind getting a message, but for my end users I would like to just change the contents so that it is less confusing. The message “No date to retrieve”/”there is no data . . . .” gives the idea that the data warehouse is empty. It’s a too technical message. It’s like your computer giving a message “Partnr 7231-A2 is above 70 degrees Fahrenheit”. If the message would end with “but this is OK” it would not give the problem-feeling.

Further my users do not know the query names, and they will have the feeling there’s something going terribly wrong. You could start by naming your queries better. “No data to retrieve in FIN_TRANSACTIONS” is much clearer than “No data to retrieve in Query4″.

In my opinion it would better to have this message only in the editing mode for a report. Thus the error appears to the one that can deal with it. I personally find the union a horrible workaround, for every change implies changing two queries. A dummy line in your data is the other way.
But the base problem is that BO gives no choice in suppressing it for the end user.

]]>