PowerShell CmdLet Old
In case you want to automate the conversion of Classic or RDLC reports or reconversion of ForNav reports you might want to use the ForNav Powershell commandlet “Invoke-ReportsForNavConvert”, which has the same capabilities as the ForNav converter – but without the user interface
Instead input is given as parameters:
| Parameter | Description | Default |
| TableDefinitions <path | url> | Path to NAV table definition or URL to Fields oData webservice | |
| Path <path> | Path to report .txt source file | |
| Destination <path> | Path to report .txt destination file | |
| ConvertRdlcReports <bool> | Convert RDLC reports to ForNav reports | false |
| RequestPageOptionCaptionML <string> | Sets OptionCaptionML for the request page | ENU=Options |
| FindReplace <path> | Path to the ForNav hint file | |
| UseRequestPage <bool> | If both a request form and a request page is defined for the report true means that the page will be used and false that the page will be used | false |
| NavCompatibility <NavCompatibilitySelection> | Sets the compatibility of the output objects. Small differences in NAV versions require that you specify the version of NAV, you wish to use with your report objects. Valid values are 2013 (use with 2013 and 2013 R2), 2015 (use with NAV 2015 and 2016), and 2017. This setting should be used instead of the old Nav2013Compatible shown below. | 2017 (this changed over time) |
| Nav2013Compatible <bool>
(deprecated) |
Sets if the report should be compatible with NAV 2013/NAV 2013 R2 or newer versions of NAV. This setting is now deprecated. Please use NavCompatibility instead. | false |
| SeparateDestinationFiles <bool> | Sets if the output should be in one file or separate files pr. report | false |
| ExportCaptions | Path to a txt file where all CaptionML strings from the report layouts is exported to. The format of the txt file is: <ReportNo>:<ControlName> <CaptionML> |
|
| ImportCaptions | Path to a txt file where CaptionML strings in the report layouts can be updated from. The format of the txt file is the same as the ExportCaptions format |
|
| Diff | Path to the destination for the diff json file | |
| Patch | Path to a json file containing the diffs that will be applied to the reports | |
| Baseline | Path to a .txt file containing the original ForNAV reports to form a basis for the diff |
Latest news
Latest knowledge base articles
-
FORNAV moves to the layout type “Custom”
-
Detect if a JavaScript record or data item record is the last record within the current filter
-
Troubleshooting when using the FORNAV reporting service for printing (Server Print)
-
Setting up Business Central for FORNAV E-invoicing and Peppol Plus
-
Using Auto Format in FORNAV layouts



