Wednesday 26 October 2011

RSV-VAL-0016 The burst query Summary cannot be a nested query

Hi Guys

Below is the extract from IBM about the error.

Problem(Abstract)An error message is returned when validating a burst report.

Symptom
RSV-VAL-0016 The burst query cannot be a nested query.

Cause
A Report Object related to the burst query is nested inside another object which is related to another query. (For example, a list nested inside another list). The burst query cannot be nested inside another query.

Resolving the problemReview the report specification, and ensure that if any nesting exists, the burst query is reflected on the outer-most level of nesting.

Steps:
It may be helpful to review the structure of the report.
From Report Studio:
1. Click View-->Page Structure
2. Expand the document structure, and review the query properties for each container (list, crosstab, etc..)
Ensure the outer-most object is associated with the query used for the bursting options.

So this is what i did to resolve it

I was using a shorcut query (A query reference) called summary and and data item from this i was using to create burst group query and burst receipeint query . I changed both burst recepeint and burst group to point to souce of this query reference and this solved the issue .I was able to burst the report .

Point to remember

Burst query should be outer most query in the nesting .So if you have a query associated with page then that is the outermost query .So the query used for bursting and query used for page should be same otherwise you will get the following error - RSV-VAL-0016 The burst query Summary cannot be a nested query

To know more about bursting .. burst qroup queries and burst receipient queries check below link of my blog

2 comments:

  1. Hi,
    I am getting the same error and I checked for the query used for bursting options and it is the same as used in multiple pages which are going to render. So what could be the possible solution in that case.

    Thanks,
    Samir

    ReplyDelete
  2. Hi,
    I am getting the same error and I checked for the query used for bursting options and it is the same as used in multiple pages which are going to render. So what could be the possible solution in that case.

    Thanks,
    Samir

    ReplyDelete