Update the way PermissionSets are defined
PermissionSets are currently defined using XML files, which have several problems: 1. They still use IDs and basically expect you to remember the IDs of every table by memory, if you want to quickly review permissions. 2. There is no autocomplete when selecting the IDs. 3. When entering an ID th...
Add a "TableRelationDisplayField" property for fields with the "TableRelation" property set.
This a very basic UX improvement: let us set which field will be *shown* in fields with the TableRelation property. Sure, If you have used NAV/BC for long enough you end up memorising all vendor, customer, salesperson, item category codes (and get used to using the Code field as some kind of des...
Add an option to load all AL projects in the VS Code workspace
When you refactor (F2) a method, or even when you are making changes to any object, the AL compilation engine only takes into account projects that you have explicitly opened (that is, where you have opened any AL file into the VS Code editor). This means that, for apps composed of several proje...
defaultApplicationArea in app.json
Yeah, when you need it, the ApplicationArea property is great. But when you are developing a per tenant extension for a customer, of an app for app source where it's all or nothing (if you install it is because you want to see all fields/actions added by the app), having to add ApplicationArea = ...