If you want to start working with an RDLC report in ForNAV, you can choose from the following different strategies, which all require that you convert your RDLC report to ForNAV.
- Use the converted layout and move sections that were misplaced during the conversion. The conversion from RDLC to ForNAV is not a 100% conversion and things like JavaScript can show errors after the conversion. In most cases you will end up with a working layout. However, it will inherit some of the structural problems from RDLC and in the long run it might not be the best option.
- Keep the dataset and AL code but delete the layout and create the layout from scratch. You can use the converted AL code and dataset when you build the new layout.
- Create a new report with the same functionality from scratch. With the features of ForNAV, you can most likely build the same report in a short amount of time. With this strategy, you end up with a clean design and a minimal dataset. This approach is good for future maintainability and runtime performance.
- Alternatively, you can convert a classic version of the report instead of the RDLC version of the same report. RDLC reports are often carried over from a classic version of NAV. If the report logic has not changed a lot since the classic report was reprogrammed in RDLC, then you can often get a better result by converting the classic report to ForNAV using the ForNAV converter.
Both classic and RDLC reports can be converted to ForNAV reports in two different ways: You can open the report text object file directly from the Designer, which will convert it when it loads the report; alternatively, you can run the report text object through the Converter. The Converter is often the best choice if you are converting multiple reports.
