nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Aggregation filtering with dataSetRow

qos

Hi there,

hope you can help us with this: we have one aggregation field using a datasetRow as filter. It works ok on designer mode but in runtime the report is generated with errors regarding that specific field.

You can find the rptdesign attached to the post.

Here is the stack trace of the report error:

The following items have errors:

Grid (id = 79):
- Can not load the report query: 79. Errors occurred when generating the report document for the report element with ID 79. (Element ID:79)
Error.ReportQueryLoadingError2 ( 1 time(s) )
detail : org.eclipse.birt.report.engine.api.EngineException: Can not load the report query: 79. Errors occurred when generating the report document for the report element with ID 79. (Element ID:79)
at org.eclipse.birt.report.engine.data.dte.DataPresentationEngine.doExecuteQuery(DataPresentationEngine.java:164)
at org.eclipse.birt.report.engine.data.dte.AbstractDataEngine.execute(AbstractDataEngine.java:267)
at org.eclipse.birt.report.engine.executor.ExecutionContext.executeQuery(ExecutionContext.java:1939)
at org.eclipse.birt.report.engine.internal.document.v4.ReportItemExecutor.executeQuery(ReportItemExecutor.java:412)
at org.eclipse.birt.report.engine.internal.document.v4.GridItemExecutor.doExecute(GridItemExecutor.java:49)
at org.eclipse.birt.report.engine.internal.document.v4.ReportItemExecutor.execute(ReportItemExecutor.java:294)
at org.eclipse.birt.report.engine.internal.document.v4.ContainerExecutor.prepareChildExecutor(ContainerExecutor.java:226)
at org.eclipse.birt.report.engine.internal.document.v4.ContainerExecutor.hasNextChild(ContainerExecutor.java:110)
at org.eclipse.birt.report.engine.internal.executor.wrap.WrappedReportItemExecutor.hasNextChild(WrappedReportItemExecutor.java:86)
at org.eclipse.birt.report.engine.internal.executor.wrap.WrappedReportItemExecutor.hasNextChild(WrappedReportItemExecutor.java:86)
at org.eclipse.birt.report.engine.api.impl.RenderTask$ReportExecutorWrapper.hasNextChild(RenderTask.java:780)
at org.eclipse.birt.report.engine.layout.html.HTMLPageLM$1.hasNextChild(HTMLPageLM.java:68)
at org.eclipse.birt.report.engine.layout.html.HTMLBlockStackingLM.layoutNodes(HTMLBlockStackingLM.java:62)
at org.eclipse.birt.report.engine.layout.html.HTMLPageLM.layout(HTMLPageLM.java:92)
at org.eclipse.birt.report.engine.layout.html.HTMLReportLayoutEngine.layout(HTMLReportLayoutEngine.java:100)
at org.eclipse.birt.report.engine.api.impl.RenderTask$PageRangeRender.render(RenderTask.java:661)
at org.eclipse.birt.report.engine.api.impl.RenderTask.render(RenderTask.java:294)
...

Thanks in advance,

qos

Find more posts tagged with

Comments

Hans_vd

Hi qos,

Seems like the Classic Models sample DB can not be reached from your server. Can you check that?

qos

<blockquote class='ipsBlockquote' data-author="'Hans_vd'" data-cid="111928" data-time="1354193922" data-date="29 November 2012 - 05:58 AM">
Hi qos, 
 
Seems like the Classic Models sample DB can not be reached from your server. Can you check that? </blockquote>
 
 
It can be reached indeed!! You can try to change, in the example provided the aggregation filter from dataSetRow to row and it works!! The problem relies on dataSetRow...

qos

Any ideas on this? Really could use your help...

Thanks

Hans_vd

Hi Qos,

I thought you had it working by changing dataSetRow to row?
Didn't that do the trick?

qos

Hi Hans,

yes, in fact changing it to row solves the problem, we had already reached that conclusion.
The problem is that we have some reports with dataSetRow already on production and working fine in similar situations (depending on the grid hierarchy) with 3.7.0.
Mavenizing the project made us change to 3.7.1(dataSetRow error on design and runtime)/3.7.2(ok on design but dataSetRow errors on runtime) and now we have these problems.
Is it a limitation of these newer versions?

Thanks,

qos

PS: grid hierarchy example attached (working on 3.7.0 but not on 3.7.1/3.7.2 as explained above)

Hans_vd

Qos,

I don't know about the versions.
The only thing I know is that we had the same problem in version 2.6.1 : it worked in the Design Editor, but not on the server. On the other hand, we did not get the "Can not load the report query" exception, that seems to have nothing to do with what's really wrong.

Maybe you can post a new question about the difference in versions in the more active "Designing BIRT Reports" forum.

qos

Thank you Hans,

I'll do that...