Warning: Payment Line table marked for removal in BC 28.0 – recommended migration path?

(3) Share

Report

Posted on by Chaima Ayadi

Hello, I’m currently working on a Business Central extension where I have a tableextension on the standard Payment Line table. After updating the AL extension / VS Code environment, I’m getting the following warning: “Table 'Payment Line' is marked for removal. Reason: Moved to the Payment Management FR first-party app. Tag: 28.0.” The warning appears several times for the same table. What is the recommended approach to handle this change? Should we replace the Payment Line table reference with a table from the new Payment Management FR first-party app, add the appropriate dependency in app.json, or is there another recommended migration path to ensure that the extension remains compatible with future Business Central versions? Also, is there a way to avoid this warning becoming an error when compiling/updating the extension in VS Code, while keeping the extension compatible with BC 28.0 and later? Could someone please clarify what Microsoft recommends for extensions curr

Categories:

Dynamics 365 Business Central

Dynamics 365 Business Central migration

All responses (7)

Answers (3)

Sort by

Verified answer

Nyakinyua 96 on at

Like (1)

Report
Copy link

Link copied!

Hi,
This is Microsoft's standard "moved to an extension" pattern as per their deprecated fields guidance, the fix is to install/depend on the new app when you upgrade.
Steps:
1.Add a dependency on the "Payment Management FR" app in app.json.
2. Update your tableExtension to target the table from its new location in that app instead of base Payment Line.
3.Check the "Obsoleted elements in base application 28.0" page on Microsoft Learn for the exact replacement object and whether it's Pending(warning only) or Removed(breaking).

On the warning: it stays a warning while ObsoleteState = Pending; it only becomes an error once Microsoft sets it to Removed in a later release. You can suppress it short-term with #pragma warning disable AL0432 , but that just delays the real fix.

Best,
Nyakinyua
Suggested answer

Chaima Ayadi 20 on at

Like (0)

Report
Copy link

Link copied!

Thank you
Verified answer

YUN ZHU 103,635 Super User 2026 Season 2 on at

Like (2)

Report
Copy link

Link copied!

Hi, hope the following helps as well.
Upgrading per-tenant extensions that conflict with other extensions
https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-pte-merge-conflict?wt.mc_id=DX-MVP-5004336
PS:
D365 Business Central : Use AppSourceCop to Detect Breaking Changes | That NAV Guy

Thanks.
ZHU
Verified answer

Grigorios Mavrogeorgis 3,638 Super User 2026 Season 2 on at

Like (1)

Report
Copy link

Link copied!

Hi, yes, you read it right. The French localisation objects are being pulled out of the base app into a first-party app, so the move is to add the dependency on the Payment Management FR app in app.json and point your tableextension at the table there. Suppressing the warning only buys you time until the obsolete state goes from Pending to Removed, then it's a build error anyway.
Get the exact app id, publisher and name from the symbols in your own container rather than from a blog post, these ids get published late and I wouldn't trust my memory on it.
One thing that catches people, if your extension also runs on non-FR customers, that new dependency now follows them too. If that's your case it's usually cleaner to split the FR part into a separate app.
► If this solved it, marking it verified helps others too.
Regards,
Grigorios Mavrogeorgis
Business Central Consultant & AL Developer
Work: Gmsoft Limited
Blog: insidebusinesscentral
LinkedIn: linkedin.com/in/gregorymavrogeorgis
Suggested answer

Chaima Ayadi 20 on at

Like (0)

Report
Copy link

Link copied!

@YUN ZHU Thank you very much for your support. I really appreciate it!
Suggested answer

Chaima Ayadi 20 on at

Like (0)

Report
Copy link

Link copied!

@Grigorios Mavrogeorgis Thank you very much, Grigorios! Your explanation was really helpful. I appreciate your support!
Suggested answer

D365BC_AmanKr 180 on at

Like (0)

Report
Copy link

Link copied!

Hello Chaima,
The recommended approach is to follow Microsoft’s “moved to an extension” migration pattern. Add the Payment Management FR app as a dependency in app.json and update the tableextension to reference the replacement table from that app instead of the Base Application Payment Line table. Also, check Microsoft’s “Obsoleted elements in Base Application 28.0” documentation to confirm the replacement object and whether the element is Pending or Removed. While it remains Pending, the message is only a warning; #pragma warning disable AL0432 can suppress it temporarily, but migrating to the replacement object is the recommended long-term solution for BC 28.0 and future versions.
Hope it will help you.
Please Verify if you found the answer helpful so that it will help others.
Many Thanks
Aman