Dynamics Community Forum Thread Details

Navigating AL Development Challenges as a Business Central Newcomer

Hello,

As a newcomer to Microsoft AL Development, I've been working with Business Central for 04 months, gradually building my expertise in this specialized programming environment.

I’m currently migrating from Dynamics NAV 2009 Classic, where we used C/AL, to Business Central Cloud Version v25 (25.0.23364.26558). As part of this project, I’ve been integrating legacy functionality, creating new tables, pages, and adapting code to work with the latest system. However, I’ve encountered an issue related to pricing.

By default, the system still uses the V15 price calculation, which we had been using in NAV 2009. The V15 implementation works as expected for now, but I’ve discovered that it’s flagged for removal in v26, which is scheduled to be released in April 2025 (Wave 1). This has serious implications for my project because key tables like 7002 "Sales Price" and 7012 "Purchase Price" are being deprecated.

Here’s an example of how the deprecation is defined in the code:

table 7002 "Sales Price"
{
Caption = 'Sales Price';
#if not CLEAN25
LookupPageID = "Sales Prices";
ObsoleteState = Pending;
ObsoleteTag = '16.0';
#else
ObsoleteState = Removed;
ObsoleteTag = '26.0';
}

The ObsoleteState is marked as Pending in v25, meaning the table is still available for use, but in v26, it transitions to Removed. This indicates that the table and all associated functionality will no longer exist. The same applies to the 7012 "Purchase Price" table.

To confirm this, I checked Feature Management and found an entry for "Feature Update: New sales pricing experience", which explicitly states that the new pricing model will become the default in v26. The feature update is labeled as:

Feature Update: New sales pricing experience | Learn more: | 2025 Wave 1 (from April to September 2025) | Automatically enabled from version 26.0.

This means that when v26 is released, the old V15 pricing calculation will no longer be supported, and any code or customizations I implement that rely on the old pricing structure will no longer execute.

This realization has put me in a challenging position. Although I’ve been making steady progress with my integrations, the impending removal of the Sales Price and Purchase Price tables in the next major version leaves me with no choice but to start refactoring now. Waiting to see what happens isn’t a viable option.

While the ObsoleteState = Removed comment suggests definitive removal, the uncertainty stems from Microsoft's historical approach to deprecation. Software vendors often maintain backward compatibility or provide migration paths. However, the explicit feature management update and clear timeline (v26 in April 2025) indicate a strong intent to transition.

This post is about my uncertainty regarding whether I need to start refactoring now or wait, and also trying to understand all of this

Sincerely,

Have a good day !

Quick Links

Leaderboard