When you start doing AL development in VSCode, you inevitably will want to convert from the very old and dusty C/AL language, to the brand new shining innovative AL language 🙂
A question I get asked frequently is: Ho Do I Create a Report in VSCode, and to me more specific, How Do I Create the Layout, being an RDLC or Word layout?
The answer is that you need to create the report object as an .al file, then you create and export the layout(s) and reference them from within the .al file.
Previously each G/L account was identified as either a Balance Sheet or Income Statement account, then based on your chart of accounts grouping would give you the reporting layout. In NAV 2017 using account categories, you can assign to the G/L account level, regardless of the begin and end total accounts ranges. For example, grouping together any operating and non-operating expenses.
One of my pet peeves about the PowerShell cmdlets that ship with NAV is the lack of built-in argument completion: the module in question knows exactly which server instances exist (after all, it has a cmdlet that lets you retrieve a list of these instances), but lacks the ability to enumerate the instance names when you specify a -ServerInstance parameter and press the Tab key.
XMLPort is a nice tool that allows you quickly import and export xml files. The tool has some shortcomings, but there is always a work around it.
For an implementation recently I had to export an xml and it could not have empty xml nodes. For example. Bellow is an xml file created by xmlport