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

Migration of rptdesign from 2.3.1 to 2.5.2

BirtRunn

I am using birt 2.3.1. Now I am planning to use birt runtime 2.5.2 for which what should be done to existing rptdesign files. I believe we don?t need to do anything special but we have to test all functionalities inside report for upgraded version. Please confirm.

Find more posts tagged with

Comments

mwilliams

Hi BirtRunn,

That is correct. There have been some changes, obviously, between 2.3.1 to 2.5.2, so you'll want to test the functionality of all reports before migrating your production environment. There may be some changes you have to make here and there before they'll run as expected.

Hope this helps.

BirtRunn

Yes that was helpful.

If I want to modify design file with latest birt version then by just opening in new Eclipse or RCP designer, it will upgrade it to latest version and then we can modify it as per our requirement. In such case Eclipse ask us if it can update it to latest version.

mwilliams

BirtRunn,

If you make a change on a report that was designed in an older version, in a more recent version and try to save it, you will be reminded that the report was created in an earlier version. Once you save the report with the newer version, it won't run in the older version without going into the XML Source and changing the version back. It still may fail in the earlier version if the change you made was something that the earlier version didn't support. If you're upgrading, this won't be that important to you. As always, you should make copies of each old report and run them in the newer version of BIRT to be sure that they run as expected before upgrading your production environment!

Let me know if this does not answer your question!