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; } } }

Formatting is now wacky

cmrdjr

Prior to our last update with BIRT all the formatting was correct with our reports. Now some of the alignment as well as some of the percentage formatting is gone. The code is still there, but when the report renders the formatting is non-existent or partial. The percentage formatting on this report is correct for some of the columns, but on one the formatting is gone for the display eventhough the report design shows that the formatting is correct.

Any ideas?

Thanks,

Eclipse
Build id: 20090920-1017

Business Intelligence and Reporting Tools

Version: 2.5.1.v20090708-9dDy89GJhLz0W7IUGJN5kAE3JjXT
Build id: v20090917-0630

Find more posts tagged with

Comments

mwilliams

2.5.1 is your current version or the previous version?

cmrdjr

<blockquote class='ipsBlockquote' data-author="'mwilliams'" data-cid="68633" data-time="1285098894" data-date="21 September 2010 - 12:54 PM"><p>
2.5.1 is your current version or the previous version?<br /></p></blockquote>
Current

mwilliams

Is the code different where it's working and where it's not working? Can you show what the code looks like that you're using? What was your previous version? If you make a simple report with the sample database with this formatting in the "old" version, does this same thing still happen in the "new" version?

cmrdjr

I have not tried to reproduce this with a new report in the sample database or our production data. These reports have been in our production environment for months and then all of a sudden they get wacky. I just took a closer look and I have to retract the upgrade comment. My production environment is now at 2.5.2 but my developement area is running the 2.5.1. The display is the same regardless of the version.
I just did an update withing BIRT and now my ojdbc14.jar is lost...GRRR Maybe it's time to just go home. Anyway here is the code for one cell that is not working and one that is working.

not working:
<cell id="10400">
<data name="NewData362" id="10401">
<property name="marginTop">0pt</property>
<property name="marginRight">5pt</property>
<property name="paddingTop">0pt</property>
<property name="paddingBottom">5pt</property>
<structure name="numberFormat">
<property name="category">Percent</property>
<property name="pattern">#,##0.00%;(#,##0.00)%</property>
</structure>
<list-property name="mapRules">
<structure>
<expression name="testExpr">row["AGG_CLSIF_BUD_TOT_PRD"]</expression>
<property name="operator">eq</property>
<simple-property-list name="value1">
<value>0</value>
</simple-property-list>
<text-property name="display">NA</text-property>
</structure>
</list-property>
<property name="resultSetColumn">ACT_MINUS_BUDGET_PCT_CLSIF</property>
</data>
</cell>

working:
<cell id="10406">
<data name="NewData365" id="10407">
<property name="marginTop">0pt</property>
<property name="marginRight">15pt</property>
<property name="paddingTop">0pt</property>
<property name="paddingBottom">5pt</property>
<structure name="numberFormat">
<property name="category">Percent</property>
<property name="pattern">#,##0.00%;(#,##0.00)%</property>
</structure>
<list-property name="mapRules">
<structure>
<expression name="testExpr">row["AGG_PRIOR_CLSIF"]</expression>
<property name="operator">eq</property>
<simple-property-list name="value1">
<value>0</value>
</simple-property-list>
<text-property name="display">NA</text-property>
</structure>
</list-property>
<property name="resultSetColumn">ACT_MINUS_PY_CLSIF_PCT</property>
</data>
</cell>

mwilliams

For the driver jar file, you'll probably just have to re-point to it through the dataSet editor to fix that issue.

As for the two cells with the same expression with one working and the other not, that is very weird. Is one of the fields possibly not of the same type as the other? I'm just guessing now. I have not seen this issue before. What was your previous version? I'll try this code in a report created with the earlier version and move it to 2.5.2 and see what happens. If you can create a report that works fine in the old version, but not in the new version, with the sample database, that'd be helpful too, probably.