What's the best way to localize a SectionReport (XML-based RPX) reports?

What's the best way to localize a SectionReport (XML-based RPX) reports?

Posted by: roman.mueller on 18 November 2024, 3:04 am EST

• 

  roman.mueller

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 18 November 2024, 3:04 am EST

  I have huge troubles to use the designer in .NET 8 projects with SectionReports (code-based). I think it’s not even working and I have to link the reports to an old .NET Framework 4.8 project, which would be really awful. That’s why I want to switch to SectionReports (XML-based).

  Up to now I used SectionReports (code-based) to create reports and was able to localize the report using *.resx or do it in code. In code it’s a bit awful and I would rather send the data as a Dictionary<string, string> to the constructor, a method or to a property. But all three “solutions” are not really working in a *.rpx because the scripts are just event based.

  What’s the best way to localize such XML-based reports? Any hint would be highly appreciated.

• 

  katyayny.raghuvanshi

  

  • Post Options:
  • Link
    Copy

  Posted 18 November 2024, 3:32 am EST

  Hi Roman,

  There is no resource file for the .rpx reports as it is a standalone report format. However, you can use the Scripts option to set report item properties based on the report’s Culture property in the Report Start event. Please refer to the attached sample report for your reference.

  We hope this helps!

  Attachment: MultiLanguageReport.zip

• 

  roman.mueller

  • Post Options:
  • Link
    Copy

  Posted 18 November 2024, 6:03 am EST

  It works. However, I thought there must be a much better approach for such a common scenario.