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

BIRT Conversion 2.3.2 to 3.7.1

megabri

I'm upgrading from maximo 7.1 that uses BIRT 2.3.2 to design reports to maximo 7.5 that is compatible with BIRT 3.7.1. If I have reports that were written in 2.3.2 is there a conversion tool that could help me or would I have to completely re-write all of my reports in 3.7.1?

Find more posts tagged with

Comments

kclark

Typically older reports work with the newer versions but you'll want to test them before putting them into production. Depending on how they are designed you might not have to modify them to much to get them working in 3.7.

megabri

<blockquote class='ipsBlockquote' data-author="'kclark'" data-cid="116766" data-time="1368560619" data-date="14 May 2013 - 12:43 PM">
Typically older reports work with the newer versions but you'll want to test them before putting them into production. Depending on how they are designed you might not have to modify them to much to get them working in 3.7. </blockquote>
So what you're saying is I can probably just upload my 2.3.2 reports into maximo 7.5? Or should I open them in 3.7 and try to run them first?

kclark

It might be easier to open them in 3.7 first to see if they need any changes before uploading them to maximo 7.5.

megabri

<blockquote class='ipsBlockquote' data-author="'kclark'" data-cid="116768" data-time="1368560859" data-date="14 May 2013 - 12:47 PM">
It might be easier to open them in 3.7 first to see if they need any changes before uploading them to maximo 7.5. </blockquote>
Ok thanks! Do you know if there's any documentation about upgrading reports?

johnw

Assuming IBM didn't change anything in the Maximo libraries for reading the data, or if you just connected directly to the database, you can just open the reports and save them using BIRT 3.7.1 designer. That would be the only step. You could script this if you needed to automate it using the Design Engine API, which might be worthwhile depending on the number of reports we are talking here.

But there were some minor changes in the engine between 2.3.2 to 2.5 that might manifest a few incompatibilities, particularly with some advanced chart operations. If you were doing basic chart operations you shouldn't see any problems running your older reports in Maximo.