Daniel Göhler prisma informatik GmbH

Please provide all tables and fields in the Business Central API like Dynamics 365 Customer Engagement Web API (https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/use-microsoft-dynamics-365-web-api). Currently you have only limited access thought the Business Central API. You need to create separate API pages for each table, which is not included in the standard Business Central API. Also, if you need additional fields that are not included in the standard API, you need to create a copy of the existing API page and add the additional fields.

In order to access all the tables in Business Central for BI without creating many API pages, it would be nice to be able to create a daily backup of Business Central and restore it to a SQL Azure instance.

Since the BaseApp will not be split up anytime soon, how about to have also the BaseApp on GitHub like the System and some Other Apps (https://github.com/microsoft/ALAppExtensions)? This would have a few advantages: - See all the changes that were made over time - This would streamline and improve the Event Request and Function Expose process, when we are able to send this as Pull-Requests. - Also, Application Enhancements and Bugfix via Pull Request where doable. - And even Translation Errors could be discovered and fix more easily.

It would be nice if unpublishing extensions was included in the Business Central Automation API so that the old apps can be unpublished after the new extensions is installed.

It would be nice if the AL Table Proxy Generator (altpgen.exe) would write all table definitions in en-US and insert the CRM translations into the xliff files.

It would be nice if the AL Table Proxy Generator (altpgen.exe) had more control over the objects to be created, such as the name of the file, the object name of the table or table extension, the object id of each individual object, and the path where the AL files are created/updated.

It would be very cool to be able to view and change the XLIFF translations directly in the Caption or ToolTip in the AL file.

It would be nice if the XLIFF files were automatically synchronised after AL: Package. Currently this is an extra step, e.g. when using XLIFFSync, which can be forgotten. Missing Translation/Changed Captions should be listed as a CodeCop Warning.

There should be a CodeCop warning if Captions of objects or fields are missing.

Currently the order changes very often in the .g.xlf. XLIFF Sync aligns the translation files to the.g.xlf. This causes git merge conflicts very often. Inserting a field in a table extension and page extension moves another unrelated block from one place to another place. A consistent order of the .g.xlf entries would be very nice.