web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested Answer

Incompatibility errors in BC v28 for "VAT Amount Line"

(3) ShareShare
ReportReport
Posted on by 4,042
How can i fix following incompatibility errors with BC version 28? any general suggestion would be helpful. The errors are due to changes in "VAT Amount Line" table. Thank you.
------------------------
Errors:
Error AL0133: Argument 4: cannot convert from 'Code[20]' to 'Boolean'
Error AL0133: Argument 5: cannot convert from 'Boolean' to 'Decimal'
Error AL0133: Argument 6: cannot convert from 'Decimal' to 'Boolean'
Error AL0133: Argument 8: cannot convert from 'Boolean' to 'Decimal'
Error AL0132: 'Record "VAT Amount Line"' does not contain a definition for 'SumLine'
------------------------
Extension code snippets:
var  VATAmLn: Record "VAT Amount Line";
VATAmLn.InsertNewLine(para1, para2, para3, para4, para5, para6, para7, para8);
...
VATAmLn.SumLine(para1, para2, para3, para4, para5);
------------------------
Reference:
I have the same question (0)
  • Suggested answer
    YUN ZHU Profile Picture
    100,974 Super User 2026 Season 1 on at
    Try the following InsertLine() method and events.
     
    Thanks.
    ZHU
  • Suggested answer
    OussamaSabbouh Profile Picture
    16,074 Super User 2026 Season 1 on at
    Hello,
    This is a BC 28 breaking change in table "VAT Amount Line": your old InsertNewLine(...) call no longer matches the current parameter list, so arguments are now shifted by position (Code[20] is landing where BC 28 expects a Boolean, then the following Boolean/Decimal values are also offset), and SumLine(...) appears to have been removed or replaced, so the fix is to open the BC 28 symbol/source for VAT Amount Line, compare the current procedure signatures, remap InsertNewLine to the new exact argument order/types, and replace SumLine with the new BC 28 calculation pattern/procedure rather than trying to cast parameters; as a general upgrade rule, wrap Base App helper calls like this behind your own local helper methods so future signature changes only require one adjustment point.
    Regards,
    Oussama Sabbouh
  • Suggested answer
    Khushbu Rajvi. Profile Picture
    22,424 Super User 2026 Season 1 on at
    You need to review the updated table definition and align your parameters accordingly, and replace SumLine with the new standard calculation logic from the base app.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,086 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 1,290 Super User 2026 Season 1

#3
AndrewThomas81 Profile Picture

AndrewThomas81 1,218

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans