Following the marketing focus blog previously published, here is the technical focused summary of day one. These are the highlights of Directions EMEA from Andrea Concato, the Development Manager at TVision.

Modern Client

The Modern Client has:

  • Role Centre Customisations
  • Bookmark and drag and drop
  • Save View List
  • Multiple Windows with Syncing between each other
  • Shortcuts and ToolTip
  • Background Posting (where consecutive series number is not required)
  • Error Log Register

Number sequence

Less blocking due to no series with new number sequence in Business Central.
In AL, you can create and manage number sequences that generate numeric identifiers for data and records. Business Central number sequences are built on SQL Server number sequences, which means that they are not associated with any tables. Instead, the application code references the number sequence object and coordinates the values across records.
The numbers in a number sequence are generated in ascending order at a defined interval. Numbers are used sequentially, but numbers can be skipped. This means that numbers used on records in tables can have gaps. These gaps, for example, can occur when transactions are rolled back or numbers are allocated but not used.

Page Background tasks

To improve the performance of a page, you can develop the page to run read-only computations and long processes asynchronously in background tasks. Background tasks make a page quicker to open and more responsive, faster for users to enter information because users are not blocked from working while waiting for the computations to finish. Typical place where you might use background tasks is on cues and pages in FactBoxes.

SystemId field GUID Replace our RecordID

The SystemId field is a GUID data type field that specifies a unique, immutable (read-only) identifier for records in the table. The SystemId field has the following characteristics and behaviour:
All records must have a value in the SystemId field.
You can assign your own value when a record is inserted in the database; otherwise the platform will automatically generate and assign a value.
Once the SystemId has been set, it cannot be changed.
There is always a unique secondary key on the SystemId field to ensure records do not have identical field values.
The SystemId field is given the field number 2000000000.

Code Sample:

myRec.SystemId := ‘{B6666666-F5A2-E911-8180-001DD8B7338E}’;
myRec.Insert(true, true);

id := myRec.GetBySystemId(‘{B6666666-F5A2-E911-8180-001DD8B7338E}’;

Why is it important:
Link and Notes
Table extensions relations
Smart Lookup


Telemetry SaaS Business Central Admin Portal ( application insight Key)
KQL new language query telemetry to get info from Azure Monitor log
New AL SessionInformation Data Type


This link points to Breaking Changes …and how to resolve them
The known breaking changes are listed from the latest major release. You will also get help to compile code against the latest version of the Business Central System Application and Base Application.


Modules have the following properties:
They separate concerns and are functionally coherent
They have stable, well documented APIs that are exposed through facades
They encapsulate complexity and hide implementation details
They have a small attack surface, which makes them easier to secure
They are faster to compile and publish, which supports a good developer experience
Their size and clear purpose allow for a code contribution model and focused design discussions

System Application

The System Application is the interface to the Business Central platform and cloud ecosystem. Currently, the collection of system application modules looks as follows: