What’s New: AL Runtime and Database (2024 release wave 1)
AL runtime and database changes in Business Central 2024 release wave 1: new number sequence methods (restart, range start), change log cleanup and an on-premises alter key method, table-level field tooltips, test field navigation links, and the move to .NET 8 and PowerShell 7.
- Number Sequence enhancements
- Change log cleanup and alter key method
- Field tooltips on table level
- Translatable text storage system
- Actionable error improvements and test field navigation
- Error handling documentation
- Runtime migration to .NET 8 and PowerShell 7
- Summary and takeaways
- Related sessions and resources
Overview
The session covers developer-facing runtime and database updates in 2024 release wave 1. Number sequences get faster next, current and exist methods (up to 32%), a restart method, and a range start method that fetches an interval in one call. Change log entry deletion is optimized for very large tables, and an on-premises alter key method disables keys for the current transaction to speed up bulk deletion.
It also covers field tooltips defined once on the table, new system tables for translatable texts, test field adding navigation links to failing data, expanded error handling documentation, and the server runtime move from .NET 6 to .NET 8 and from PowerShell 5 to PowerShell 7 with a backward compatibility bridge.
Key points
- Number sequence next, current and exist methods are up to 32% faster. A new restart method resets a sequence to a given number without dropping and recreating it.
- The range start method gets an interval of numbers in one call, so a range of 100 needs 1 database call instead of 100.
- The alter key method disables keys for the current transaction to speed up bulk deletion of change log entries. It is marked on-premises only, and keys are re-enabled when the transaction ends.
- The force order and loop join server settings are removed in this release. They were deprecated in version 23.
- Field tooltips can be defined on the table and are inherited by pages using the field. Page-level tooltips can still override them.
- Test field adds a navigation link to failing data when conditions are met: read permission, available drill down page ID and card page ID, and a target that is a different page or record.
- The runtime moves to .NET 8 and PowerShell 7. A bridge through the nav admin tool relays PowerShell 5 calls, but scripts that import assemblies directly may need minor changes.
Features
| Feature | Status | At |
|---|---|---|
| Number sequence next/current/exist methods performance | status not stated | 0:37 |
| Number sequence restart method | status not stated, demoed | 0:57 |
| Number sequence range start method | status not stated, demoed | 1:28 |
| Change log entry cleanup optimization | status not stated | 2:25 |
| Alter key method for on-premises | status not stated, demoed | 3:05 |
| Removal of force order and loop join server settings | status not stated | 4:32 |
| Field tooltips on table definition | status not stated, demoed | 5:07 |
| System tables for translatable texts | status not stated | 7:09 |
| Actionable errors with test field navigation | status not stated, demoed | 9:04 |
| Error handling documentation expansion | status not stated | 10:58 |
| Runtime migration to .NET 8 | status not stated | 11:50 |
| PowerShell 7 migration and backward compatibility bridge | status not stated | 12:30 |
AL objects mentioned
As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.
- other “number sequence” at 0:37
- other “change log entry” at 2:25
- other “test field” at 8:44
- table 98 “General Ledger Setup” at 9:45
- other “currency card” at 10:18
Quotes
- 0:37 “next current exist methods are up to 32% faster”
- 1:48 “so you’re basically saving a datab base call for every time you need a number so if if you have a range of 100”
- 2:25 “change log entry tables growing to very large sizes to the point where even setting up retention policies would time out”
- 5:07 “with this release wave as developer you can now Define field tool tips once on the table and any page uh that that use”
- 9:04 “we’ve added new capabilities to test field so that it can add link to add a navigation link to the failing data”
- 12:10 “for this release we have switched to net 8 which is a faster and more efficient runtime”
- 12:30 “with doet 8 we’re moving to Powers shell 7”
Disclaimers in the video
- 3:05 preview: new method which for now is mar for on premises
- 5:48 not-in-this-release: that’s science fiction not coming in this release wave
- 6:29 coming-later: I’m afraid it didn’t make it for this release but um it will go out with a later um compiler update
- 13:22 coming-later: will deprecate Parell five within the next years
Presenters (as heard): Kenny Pidan, Yan M Peterson.
