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 tables showing incorrect values

Shiny Ram

<p>Hi,</p>
<p> </p>
<p>I am newbie here. We are using BIRT 4.3.1 and data source for the report is xml and xsd files. We have a problem with rptdesign files where incorrect data(aggregation using COUNTDISTINCT,SUM) is displayed in the client environment which is of same version but different xml/xsd files. But not able to replicate the issue on our local machines with same rptdesign files. Can someone please advice.</p>
<p> </p>
<p>Working Report,</p>
<div>Engineering & Works Services 0 13 41 2 56</div>
<div>Assets Engineering 0 8 21 0 29</div>
<div>Works 0 5 20 2 27</div>
<div> </div>
<div>Not working Values</div>
<div> </div>
<div>
<div>Engineering & Works Services 0 0 0 0 0</div>
<div>Assets Engineering 0 0 0 0 0</div>
<div>Works 0 0 0 0 0</div>
</div>
<p> </p>
<p>Thanks,</p>
<p>Shine</p>

Find more posts tagged with

Comments

GLO_FR

<p>Hi,</p>
<p> </p>
<p>what version of BIRT are you using ?</p>
<p> </p>
<p>Did you test it with the client <span style="color:rgb(40,40,40);font-family:'Source Sans Pro', sans-serif;font-size:14px;">xml/xsd files ?</span></p>

Shiny Ram

<p>Hi , Thanks for replying.</p>
<p>Actually the issue was with version difference. Client recently upgraded the BIRT to 4.3.1 and none of their design files had version="" token in xml source. So when the design files were opened in new version of BIRT we get the notification to upgrade files which will in turn change the aggregation tables. So the solution was to add the version="3.2.23" token back before opening in BIRT 4.3.1. Client previously was on 3.7.2. </p>
<p> </p>
<p>Aggregation tables used to change from <span style="color:#0000ff;">count_high</span> c<span style="color:#ee82ee;">ount_medium</span> ..to <span style="color:#0000ff;">count_high count_high count_high</span>...</p>
<p> </p>
<p>Regards,</p>
<p>Shine</p>

GLO_FR

<p>Hi Shiny ram,</p>
<p> </p>
<p>What do you mean with <span style="font-size:14px;font-family:'Source Sans Pro', sans-serif;">count_high</span><span style="font-size:14px;font-family:'Source Sans Pro', sans-serif;"> or c</span><span style="font-size:14px;font-family:'Source Sans Pro', sans-serif;">ount_medium</span><span style="font-size:14px;font-family:'Source Sans Pro', sans-serif;"> ??</span></p>

Shiny Ram

<p>Hi ,</p>
<p> </p>
<p>Sorry I cannot post more information, </p>
<p> </p>
<p>In the aggregation builder,</p>
<p>Display Name : Count_high</p>
<p>Function; COUNTDISTINCT</p>
<p>EXpression : row(SomeNo)</p>
<p>Filter condition: datasetrow(Somevalue=HIGH)</p>
<p>Aggregate : On a Group</p>
<p> </p>
<p>similarily we have different aggregation columns based on filter condition value=medium,low..etc.</p>
<p>But after the upgrade all of them changed to same aggregation column for e:g count_high</p>
<div> </div>
<div>Thanks,</div>
<div>Shine</div>

GLO_FR

<p>Hi,</p>
<p> </p>
<p> </p>
<p>when you update your report manually and re-set the aggregation type correcly (count_high-> count_high, count_medium -> count_medium....), does it work as expected ?</p>