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

Resolve error in Business Central extension

(1) Share

Report

Posted on by Hagru

311

Hello! I got a mail from Business Central telling me that an old extension we have is not compatible with version 24.0, and I need to fix it. The error I am getting is this:

"src/tables/Job.tabext.al (63,22) - Error AL0155: A member of type Field with name 'Location Code' is already defined in Table 'Job' by the extension 'Base Application by Microsoft (24.0.16410.21216)'.",

"src/Pages/JobCard.pageext.al (67,19) - Error AL0155: A member of type Field with name 'Location Code' is already defined in Page 'Job Card' by the extension 'Base Application by Microsoft (24.0.16410.21216)'." ] } ]

I totally get the errors, however I am unsure about how to resolve it, because I assume we would like to keep the data in the field, so removing it is probably not an option, and renaming it makes the upload fail, because Business Central can't find the field 'Location Code', and removal of the field is not allowed.

What is the best way to resolve this?

I have the same question (0)

All responses (6)

Answers (0)

DigiTecKid 56 on at

Like (0)

Report

Hello @Hagru,

I have this same issue in an extension from a client I've picked up. Did you find a solution for this yet?

Was this reply helpful? Yes No
DigiTecKid 56 on at

Like (1)

Report

I found this, but I'm afraid the Configuration Package will be too large to work correctly...

Upgrading Per-Tenant Extensions that conflicts with other extensions - Business Central | Microsoft Learn

Was this reply helpful? Yes No
Suggested answer

Yi Yong 2,563 Super User 2025 Season 2 on at

Like (0)

Report

Hello,

If there are changes made to the table then you need to upload the extension with 'Schema Sync Mode' as 'Force'.

However, keep in mind that this poses a risk and you need to ensure the changes made will not cause the loss of data.

I suggest you read through this blog first.

https://yzhums.com/18755/

Was this reply helpful? Yes No
Suggested answer

Gerardo Rentería Ga... 25,225 Most Valuable Professional on at

Like (1)

Report

hi

I hope this can help you: Dynamics 365 Business Central: again about obsoleting fields – Stefano Demiliani

Best

GR

Was this reply helpful? Yes No
Suggested answer

Sami Ullah 315 Moderator on at

Like (1)

Report

To resolve the compatibility issue with your Business Central extension caused by the "Location Code" field being already defined in the Base Application, you only need to either remove the field definition or rename it, then redeploy the extension with a force sync.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 95,720 Super User 2025 Season 2 on at

Like (1)

Report

If this is an AppSource Extension, you can only contact Microsoft to resolve it.
If this is a PTE, you can force synchronization using the following method.

Business Central 2021 wave 2 (BC19): In-depth testing for Force Sync mode in Production Environment (Renaming tables, Renaming fields, Changing field type…)

https://yzhums.com/18755/

In addition, when extending the standard table, it is very important to add a prefix or suffix.
You can also avoid this problem by using the latest namespaces. More details: https://yzhums.com/42262/

If you are concerned about data issues, you can export it using Configuration Package, update the program, and then import it.

Hope this helps.

Thanks.

ZHU

Was this reply helpful? Yes No