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

Duplicate Action defined in dependent App

(5) Share

Report

Posted on by MR-05121044-0

Hello Community Members,

We have two extensions published to appsource.
eJewelry_core and EJewelry_POS
eJewelry_Core is dependency for eJewelry_POS
we have one action named “EJW Payment Information” in eJewelry_POS app.

Accidently we copied the same action to eJewelry_core and published to appsource.
As its not dependent on eJewelry_POS it got published.

Now we can not upgrade client environment to newer version.
Microsoft upgrade to 27 is getting errored out as its trying to upgrade eJewelry_Core to latest version available. This is failing due to duplicate action name.

At some point of time Microsoft will uninstall eJeewlry_Core to force upgrade to BC27 and we are at threat to loose all the client data.

Any clue will be highly appreciated.

Thanks in advance,

Miftaur Rahaman

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

Shyam Gurjar (BC Tech) 5 on at

Like (0)

Report
Copy link

Link copied!

Hello,
I have faced similar issue for upgrading to newer version. There are 2 things you should know:
1. It wont delete client data even if it uninstalls the extension forcely. Data is always there in SQL and will be fetched when you re-publish the extension.
2. Fix the extension and re-publish it . It won't have any risks as well. Also if code is not there at your end then try downloading source from extension management.

Was this reply helpful? Yes No
Suggested answer

Mohana Yadav 61,170 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Create a new version of app with the fix and publish it to AppSource.

Was this reply helpful? Yes No
Suggested answer

Kamal Khakhkhar 2,491 on at

Like (2)

Report
Copy link

Link copied!

Hii There as per requirement you can remove it in main extension if you want to share it in dependent app only . or you want to give that action with main app then remove it from dependency (child) app.

if you found your answer mark it answered.

Thank You.

Kamal Khakhkhar.

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 10,875 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hello,

Your AppSource apps both define an action named “EJW Payment Information.”

BC 27 now treats duplicate action names across extensions as a fatal AL0155 error, so Microsoft can’t upgrade the tenant.

Fix = release new AppSource versions where only one extension contains that action name.

The other extension must either:

mark its old action as Obsolete, or

rename it (keeping caption if needed), but keep the old one as Obsolete to avoid breaking AppSource rules.

Once those corrected versions are published, Microsoft can upgrade the environment normally, and nothing gets uninstalled.

Regards,

Oussama Sabbouh

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

Aman Kakkar 2,977 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi @MR-05121044-0,

You can try below mentioned two approaches -

1. If you can remove the action in the base App and publish it by increasing the version of your base app (eJewelry_Core ), then go ahead and publish it. You will be able to publish the POS App as well after the eJewelry_Core app is published.

2. If you are facing any difficulties in removing the action from the Core app, you can make the action button in the Core app to be hidden by adding this property - "Visible = false;". Now in the POS App, create a new action button with the same name and add underscore in it's name at last. For example if the name was "Action_01" then you can name it to "Action_01_". And change the caption of the action button to be the same as original action button that you made Visible = false in Core app.

These are the two ways you can save your apps. In either way, you need to publish the Core app first by increasing it's version and then you need to publish your POS app.

Do mark as verified if this helps.

Aman K

Was this reply helpful? Yes No