Skip to Content

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:

1.JPG

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

2.JPG

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:

3.JPG

The query will look like this NOW:

(

SELECT

<table_name>.<column_name>

FROM

  <table_name>

WHERE

  <table_name>.<column_name>=  ‘124’

UNION 

SELECT

  ‘ ‘

FROM

  <table_name>

)

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:

4.JPG

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

To report this post you need to login first.

4 Comments

You must be Logged on to comment or reply to a post.

  1. Mahboob 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?

    Thanks,
    Mahboob Mohammed

    (0) 
    1. Yuvraj Singh 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.

      Regards,

      Yuvraj

      (0) 

Leave a Reply