Opening old report corrupts the file.

[Andrew]

Hi

Have an old project (few months old using 19.0.25.313) running perfectly. The customer wanted a small change to a report.

On my development PC is the new 2025 Q3 Reporting software.

I opened the report in the new Designer, made the changes and they previewed OK.

Moved the report file .trdp, back to the server no I get the error...

Unable to get report parameters. Report 'rpt_LowStock.trdp' cannot be resolved.

Surely the Report Designer MUST be backwards compatible???

Thanks

 

[Andrew]

OK, So I had to re-install Reporting 2025 Q1 on my dev machine.

I then used the Standalone designer within there to open the report.

An error immediately popped up

Luckily I had a backup copy!!!

Amended the report as per the customers requirements and uploaded to the server.

All work fine!

Why does the designer always force you to upgrade? When you have old projects you should not necessarily have to do this!

[Justin]

Hello Andrew,

Indeed, the Declarative Type Reports have a Schema Version that corresponds to the version of Reporting that was used to create or updated them.

Further, with each release of Reporting, improvements are made to the Designer and a new version of the Designer is included with the release. While the Reports are backwards compatible, meaning older reports can be opened with newer Designers, they are not forward compatible. Meaning older Designers cannot open Reports with a schema version that did not exist yet when this version of the Designer was created. 

When any modifications are made to a Report, the schema version will be updated to reflect the version of the Designer used to make these changes.

If a Report schema was updated unintentionally, you may follow the steps in Open reports created with a newer version of the Standalone Report Designer to manually downgrade the schema version of the Report. 

Regards,
Justin
Progress Telerik