Small and medium business | Business Central, N...

Issue with TableExtension ID Conflicts and Renumbering in AppSource Validation for Business Central

(7) Share

Report

Posted on by FB-19121630-0

Hello everyone,
I’m facing a significant issue during the certification and publishing process of two AL extensions for Business Central on Microsoft AppSource, and I hope someone can help clarify the correct approach.
I have two apps, App X and App Y. App X is indipendent from Y, otherwise app Y depends on X.

In App X, I added a tableextension with ID Z.
Later, in App Y (which depends on App X), I also added a tableextension with ID Z.

Because of this, AppSource validation now fails for App Y, with the message indicating that the tableextension ID Z already exists in App X.
To resolve the conflict, I attempted to renumber the tableextension in App X. However, after changing the ID, AppSource now returns the following error:

"The tableextension with name '[..]' and ID 'Z' was found in the previous version, but is missing in the current extension."

At this point, I’m unsure what options I have. My questions are:

Is it possible to force the renumbering of a tableextension ID in App X?
This would be the ideal solution for us, but I’m not sure whether AppSource allows such changes without treating them as breaking changes.

Is there an official or recommended procedure for handling ID renumbering in existing published apps?

Thank you in advance!

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (6)

Answers (0)

Sort by

Suggested answer

Nitin Verma 21,812 Moderator on at

Like (0)

Report
Copy link

Link copied!

I think you should do the following:

Keep the tableextension in App X
Remove the tableextension entirely from App Y
Access the extended fields in App Y normally (this is fully supported)

Let me know if that works.

Was this reply helpful? Yes No
Suggested answer

FB-19121630-0 16 on at

Like (0)

Report
Copy link

Link copied!

Hi Nitin,
Thank you for your suggestion!
I cannot remove the tableextension from App Y because App Y is already published on AppSource as well.
Do you know if deleting a tableextension object from an already published extension is permitted?

Thank you!

Was this reply helpful? Yes No
Suggested answer

Dhiren Nagar 2,890 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi,

You need to change the object id of tableextension in App Y, if any version of App Y is not in the app source with this object id. This will allow both apps to be published.

I think compilor would also have given you error before publishing Y. So i guess Y is still not updated to Appsource.

If Y is also already published and you can not remove the object id, then you need to follow the deprication process. Using Obsolete property to remove the object and fields from one of the app and adding it in another app. Ideally looking at the scenario fields from Y should go to tableextension of X.

Try this and see.

Regards,

Dhiren.

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 17,503 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hello,

You cannot renumber a published tableextension and have AppSource accept it as a normal update—object IDs are part of the object’s identity, so changing them is treated as a breaking change, which is why AppSource complains that the old tableextension is “missing.” There is no supported way to force this. The correct and supported solution is to keep the tableextension ID in App X unchanged and renumber the conflicting tableextension in App Y, since dependent apps are installed together and must have unique object IDs across both apps. Microsoft’s guidance is clear: never renumber tableextensions after first release; instead, plan separate ID ranges per app upfront. Obsoleting applies to fields/objects, not to safely “moving” a tableextension to a new ID.

Regards,

Oussama

2 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

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

Like (2)

Report
Copy link

Link copied!

As far as I know, this can only be resolved by contacting Microsoft. In the past, when partners encountered situations where field names and standards were duplicated, Microsoft also helped them resolve the issue.

Hope this can give you some hints.

Thanks.

ZHU

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

Khushbu Rajvi. 22,792 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

I agree with Zhu, raised ticket Microsoft will help.

Was this reply helpful? Yes No