Report Auto Transformation Tool


Based on our long experience in upgrading NAV to the latest versions we found out that a lot of time (sometime 40% of project) spent on report transformation. We decided to automate this process first of all for our internal use. By the time after improvement tool including new features it was decided to share tool to NAV community.

Tool helps us to make transformation much easier and faster. The most of hand work is now automated. The only things developer left to do is to resolve conflicts which is not supported by  NAV 2017 (Like Transfer Header/Footer).

Now we are ready to share our tool with any freelance developer or MS Partners who make report transformation. Easy to use tool after 2 steps in 5 minutes can give quick result.



Tool is working as external web service. So it is not required any installations on Dev environment.

Tool requires from developer

  1. Upload  .txt file with report objects Classic NAV (Prior 2009R2).

  2. Upload Field/Keys data in XML format from target NAV (2013R2+) database. (XMLport is supplied). Field data required to get information about custom field names, their types to generate RDLC data of report as much as actual.


As result of tool developer can download .txt file with converted reports RDLC designed for target NAV (2013R2 +).



To try it for free please fill in registration form.
You will get an Email with instuctions and links to start using report transformation.



Navision Report transformation tool from Classic NAV  to RDLC design.

Standard NAV way to transform report. Converted report does not require any additional setups in NAV, no external automations, no non-standard report designer extensions. Import  .txt file with converted reports to NAV is a maximum effort developer need to do.



Free usage allows you to transform 1 report per time

and limited number of reports transformed per day (up to 5).
Trial period is 1 month long

Free proposal is possible till 1 June 2018.


Requires developers review report in NAV designer. RUN report with different options, filters and compare Classic and RDLC variant.
There is a set of unsupported features accepted by Microsoft that should be fixed manually.
Then adjust groups, remove minor or cosmetic bugs, Adjust code to New NAV functionality.

Paper size property should be adjusted manually;



Tool is supported by our team. All issues/bugs are fixed with shortest time as possible.

RDLC server is set with NA localization. Some language symbols may be corrupted on specific localizations. Create request to support team to setup specific reagional settings.


RDLC result presented as it is. No additional/manual fixes are included result report.
If transformed RDLC is imported with error to MS NAV 2017 environment or user gets compile error on RDLC SWP-Group fix it manually and send result to email.



Transfers layout to New RDLC style
Transfers code on most of triggers.

Formats numbers, dates, fonts, styles to new RDLC standards.

Refactor Header/Footer sections to create RDLC header/footer.

Deletion of unused variables for the transformed report.

Shape controls transformation with appropriate BorderWidth value.





“No Report Header GetData”\“No Report Footer GetData” - allows to create Page Header texboxes with dynamic expressions (as a standard SetData\GetData functionality been used in document type reports).


“Create Report Tablix” - Forces creation of tablix with appropriate groups using primary keys for tables which are source for every particular dataitem, othervise rectanle with controls will be created to place report controls.


“Add Static Header” - This feature allows to have first Header section controls from classic on the Page Header rdlc section after transformation. Built-in fields User!UserID and Globals!PageNumber is used while upgrading USERID and CurrReport.PAGENO values.


“Migrate Showoutput” - allows to have parsed sections code and additional Booleans created to set appropriate Row Visibility in rdlc table. (Should be used only with “Create Report Tablix” selected).


“Use Field Structure” - should be selected to use loaded information about Fields (imported previosely to Tool memory) and assign decimal formats.





Features which are not supported by the tool:

-          TransferHeader\TransferFooter sections transformation;         

-          Standard code redesign (document dimensions, kitting, excel buffer code);

-          2009 rdlc is not transformed to target. Classic structure is used for conversion;



Save time on report transformation. From Classic to RDLC style.