Navigate by "Reason Code"
We use "Reason Code" standard field to fill it with a valid "Expedient No." (a custom entity). This "Reason Code" links Purchases & Sales Documents, Pre-Documents and Entries with our Expedient so we have defined a custom page to "Navigate by Reason Code" and put an Action to call it in all this...
Add a 4th optional parameter to MODIFYALL keyword to run Field's OnValidate trigger
I suggested this in https://github.com/microsoft/AL/issues/6402: I 've always wondered why the ModifyAll() keyword has an optional third Parameter to execute the OnModiy() trigger and does not have another to optionally execute the OnValidate() trigger of the field. Actual: procedure ModifyAll(...
Make COUNTAPPROX really useful with SQL WITH (NOLOCK) modifier
The COUNTAPPROX statement in Navision / Business Central is one of the most useless out there today because it provides a value that is very different of the real value. The SQL SERVER low-level implementation of COUNTAPPROX is not at all clear or non-existent in the official documentation: htt...
Be able to setup Unrealized VAT behaviour independently for Sales and Purchases
Companies in Spain sometimes only have a few Vendors in which the legal due of VAT occurs at the time of posting the Payment and not the Invoice. Activate the "Unrealized VAT" field in "General Ledger Setup" table changes the behavior of Sales as well as Purchases simultaneously. Further, this...
Split some table settings for Sales and Purchases with a TableRelation filter
Currently, the records in the "VAT Business Posting Group" and "VAT Posting Setup" tables are valid for the entire application and, a priori, it is possible to establish configurations in the Customer and Vendor tables configured by the Sales and Purchasing managers respectively. However, the Fi...
Show/Hide "Item Variant Code" fields system wide by configuration
When a Customer needs to work with "Itrem Variants", we find that the corresponding field is not visible by default on any standard page throughout BC.
As a developer, I could spend my time defining a custom Extension where there would only be objects of type PageExtension fro...
API Pages: output fields vs input fields vs internal fields (not visible)
In the API Pages, at the field level, we currently find that almost none of the available properties actually work, even though the compiler and the CodeCops do not warn you that they will not work...
We speak, for example, of the NotBlank property, which only...
Avoid SaveValueToDatabasePromptly new behaviour with a new DelayedModify property in pages and pageexts
I think this new behaviour can break existing code and be a real pain in Document Pages for example...
I don't think the solution should be an administration setting... and less that it should be available only OnPrem...
As BC developers, I think we will need ...