Appsource validation fails for BC27 because a chartpart is removed

(6) Share

Report

Posted on by mbazioss

Hello,

We have an app on appsource that contains 3 pages with chartparts, as shown below

chartpart("270-01"; "270-01")
{
Visible = false;
ApplicationArea = All;
}

When we try to upload our app in appsource then microsoft validates the new .app for both versions BC26 and BC27.
When we remove the chartparts from the page then during appsource validation we get following error.

The chartpart with name '272-01' defined in Page 'XXX' was found in the previous version,
but is missing in the current extension. This will break dependent extensions.

If we dont remove it then we get appsource validation failure because chartparts do not exist in BC27.

I tried following approach

#if BC26
     chartpart("270-01"; "270-01")
     {
         ApplicationArea = All;
         Visible = false;
         ObsoleteState = Pending;
     }
#endif
,but still get following issue during appsource validation for BC27.
The chartpart with name 'XXX' defined in Page 'YYY' was found in the previous version, but is missing in the current extension. This will break dependent extensions.
 
Please mind that in BC27 chartparts are totally removed.
 
Does anyone know a way to fix this?
Thanks in advance,

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (3)

Answers (1)

Sort by

Verified answer

Pallavi Phade 5,639 Super User 2026 Season 1 on at

Like (5)

Report
Copy link

Link copied!

Namaste @mbazioss

Can you fix as per below image . Can you make as normal part instead of chartpart .

Below link for fixing the issue . I refered this blog

https://www.waldo.be/2024/04/30/generic-charts-forgotten-but-not-gone/

Below link for reference - where obselete property can be appplied

https://divyeshchittenavbc.wordpress.com/2019/10/18/how-to-set-obsoletestate-and-obsoletereason-in-business-central-wave-2-release-msdyn365bc/

Please verify the answer if it helped .

Regards

Pallavi Phade

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 101,250 Super User 2026 Season 1 on at

Like (4)

Report
Copy link

Link copied!

Hi, hope the following helps as well.

Best practices for deprecation of AL code

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-deprecation-guidelines?wt.mc_id=DX-MVP-5004336

Thanks

ZHU

Was this reply helpful? Yes No
Suggested answer

Rishabh Kanaskar 6,227 Super User 2026 Season 1 on at

Like (6)

Report
Copy link

Link copied!

Hi,

In BC27, chartparts were completely removed, but AppSource validation still checks for backward compatibility. There’s no way to “conditionally remove” them for AppSource; using #if BC26 only prevents compilation, but the previous version’s metadata still exists in the older app, triggering the validation error.

Recommended approach:

Mark the chartpart as obsolete instead of removing it.

Use:

chartpart("270-01"; "270-01")
{
ApplicationArea = All;
Visible = false;
ObsoleteState = Removed;
ObsoleteReason = 'Removed in BC27';
}

This keeps the object in the extension for AppSource validation but makes it non-functional in BC27.

Direct deletion isn’t allowed if it existed in the previous published version. Obsoleting is the supported method for BC27 AppSource compatibility.

Thanks

Rishabh

Was this reply helpful? Yes No