Migrating Report Templates from 2017.2.3 -> 2024.3.3

[microbio4884]

Hello,

I am on the process of migration from 2017.2.3 to 2024.3.3, I have updated the nuget packages and the UI loads, however when I try to use my existing templates (.mrt) the report loads but as soon as I interact with the designer it gives me an error "Your session has expired", I am not sure but this might be due to the .mrt templates being so old, is there a way to migrate the old .mrt templates to the new 2024.3.3 version ?


Thanks in Advance

[Lech Kulikowski]

Hello,

It should work correctly.

Please send us a sample report with test data that reproduces the issue for analysis.

Thank you.

[microbio4884]

Hello,

After a few tries and some fixes I have been able to have the old report templates from version 2017.2.3 running on the 2024.3.3 however there is what I believe a couple of problem that I am not sure how to address.

The report definitions are stored in .json format in a database column and these definitions were generated by the 2017.2.3 javascript side and now we are loading those on the .NET version of the engine.

The 2 main problem that remain are:
- The 2017.2.3 dictionary uses the "relationId" field to link Parent -> Child while the 2024.3.3 uses "_ParentID" when I generate, so old reports are missing the relationship field
- There is a few calculated variables that use what seems to be JavaScript expressions but now those are being compile and executed by .NET hence compilation fails

What would be the best way to address these problems?

Will put together a sample and attach it here for you guys to look at

[Lech Kulikowski]

Hello,

Please send us a sample that reproduces the issue for analysis.

Thank you.

[microbio4884]

Hello Support,

Attached is a sample I put together as realistic as possible that showcase the errors I am experiencing as well as the approach I am taking to be able to run the 2017.2.3 reports on the new 2024.3.3 engine.

My goal is to load and run the old report without trying to migrate or modify then since we have a lot of customers customized reports that we would then have to transform or migrate.

If you could please take a look as soon as possible, since this now a bottleneck on our production environments

[microbio4884]

Hello Support

Any updates on the above issues?

Thanks in Advance

[Lech Kulikowski]

Hello,

How can we run your project and reproduce the issue?

Thank you.

[microbio4884]

- Run the Project
- Click on the Designer
- Click on Check Issues
- Scroll thru the list and you will see the Expression Errors that prevent the report from running correctly

You can also after loading the report on the code is use the

report.Compile();

This will give you all the report errors

[microbio4884]

Here is an screenshot on how to modify the sample to introduce the report.Compile(); statement and when you run the application and go to the "Viewer" link at the top it will execute the code end-up in an exception and you will see all the errors on the exception message.

[microbio4884]

Hello Support,

Do you have any updates on how is this progressing ?


Regards,