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

Community site session details

Session Id :
Dynamics 365 Community / Forums / Small and medium business | Business Central, N... / Completely remove fiel...
Small and medium business | Business Central, N...
Unanswered

Completely remove fields with same name in separate apps

(0) ShareShare
ReportReport
Posted on by Y_A 375
Hi all, 
 
We have 2 separate apps published on AppSource and we ended in a situation where a field with the same name in the same table extension exists in both the apps. 
Upon installing the app this is failing due to this issue as it finds the same field in the same table twice.
We have obsoleted the field in one of the apps with Obsolete State set to REMOVED and published to AppSource. Upon installation, the same erorr is still being returned. 
 
What is the best way to proceed in this case? Can the field be completely removed (i.e. remove the code) from the app in which we have obsoleted it? 
 
Thanks in advance. 
Categories:
Dynamics 365 Business Central
I have the same question (0)
  • Teagen Boll Profile Picture
    Teagen Boll 40 on at
    Completely remove fields with same name in separate apps
    The fields should be set as different names. But you can make them have the same Caption - Caption property - Business Central | Microsoft Learn
     
    And it's recommended that you also set the Visible property to false for the older field - Visible property - Business Central | Microsoft Learn
  • Suggested answer
    Gregory Mavrogeorgis Profile Picture
    Gregory Mavrogeorgis 450 on at
    Completely remove fields with same name in separate apps
    Hi,
     
    Why it still fails: ObsoleteState = Removed doesn’t drop the field. The installer still sees two fields with the same technical name/ID on the same table → collision.
    Best fix now: Pick which app “owns” the field. In the other app, rename the legacy field’s technical Name (and, if needed, change its ID) to something unique, keep it Removed and hidden, and add a tiny upgrade codeunit to copy any data to the owned field. Publish that.
    Can we fully delete it? Physically removing a field is a breaking schema change on AppSource and usually blocked unless you go through Microsoft’s breaking-change process. Safer to keep the legacy field hidden/removed.
    Future-proofing: Use a unique prefix per app and enable AppSourceCop/CodeCop to prevent cross-app name clashes.
     
    If you have found this help full please mark it as verified

     

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Pallavi Phade – Community Spotlight

We are honored to recognize Pallavi Phade as our Community Spotlight honoree for…

Congratulations to the October Top 10 Community Leaders!

These are the community rock stars!

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

#1
Sumit Singh Profile Picture

Sumit Singh 2,163

#2
OussamaSabbouh Profile Picture

OussamaSabbouh 1,908

#3
YUN ZHU Profile Picture

YUN ZHU 1,878 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans