Skip to Content
Author's profile photo Former Member

How to suppress “no data to fetch” warning message?

Hi All,

We must have come across such scenario in which we get this warning message when our query does not return any data.

In some scenarios, this message is not acceptable for customers and they wish to suppress it.

Speaking about this warning message, it is By-Design in BusinessObjects and cannot be suppressed by checking or un-checking any option in BusinessObjects XI 3.x;  however, it is possible to avoid it.

There could be multiple approaches to achieve this;  however, according to me, least expensive approach is to create a Dummy object and insert a Combined Query. (for users who does not have right to edit SQL; however, can create objects in universe)

For example, let’s take below scenario:

Report is not returning data due to an unsatisfied condition applied:


In order to avoid this, create a Dummy object as follows:


Choose any table under Tables which you are using in First Query and assign it to Dummy object.

NOTE: This will only work if the first query in combined query is returning Character type data.

Add a  combined query using UNION operator and insert this object as follows:


The query will look like this NOW:







  <table_name>.<column_name>=  ‘124’



  ‘ ‘




After running the query, “no data to fetch” warning message wont come anymore as it will return blank as result.

What if first query is returning numeric value??

In this case, we can define the Select statement of our Dummy object as an integer say 1 instead of  ‘ ‘(space). This will create a Numeric Dummy object.

However, this will return 1 as result on report.

How to handle this?

Put an alerter in the report which will return a blank space and assign it to the specific column which is returning 1:


I hope this will be useful for users who have just started working with WebIntelligence.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Krishna Chaitanya
      Krishna Chaitanya

      Good one...  Cheers Krishna Chaitanya.

      Author's profile photo Former Member
      Former Member

      Hey good one...very intresting and new info..

      Thanks for sharing..:)

      Author's profile photo M Mohammed
      M Mohammed

      Hi Yuvraj,

      Combined queries requires same number of objects & data types in all positions (in all the combined queries) isn't it? So, that means, we'll have to create as many number of dummy objects (dimension(s), detail(s) & measure(s)) as the number of object we're getting data for in the 1st combined query. Isn't it?

      Mahboob Mohammed

      Author's profile photo Former Member
      Former Member
      Blog Post Author

      Hi Mahboob,

      Yes, you are absolutely correct. That is only when you dont have the rights to edit the query.

      Else you can straight away edit and put a UNION with dummy values in SELECT statement.

      Hope it answers your question.