Skip to main content
Solved

Multiple Customization Projects to add no-code Actions to the same screen

  • October 20, 2025
  • 6 replies
  • 52 views
Graeme Laughton-Mutu
Semi-Pro I
Forum|alt.badge.img+1

Is it possible to have no-code Actions from multiple customization projects show on the same screen
I’m only seeing the no-code action from the published customization project with the highest level.

Do all no-code actions per screen need to be in one single project?
Or is there a way to have them all added to the screen, from their various projects?

 

Example:

Project 1 (Level 50) - Sales Orders > Action A
Project 2 (Level 60) - Sales Orders > Action B

When both projects are published, only Action B shows on the Sales Order screen.
When only Project 1 is published, only Action A shows on the Sales Orders screen.

Best answer by aiwan

​@Graeme Laughton-Mutu 

 

Unfortunately, I believe you will have to extract the actions into a separate customisation project.

 

If they are in compiled .dll’s this makes it easier as you can add the actions into a new project, with no-code actions, the logic for these is usually contained within the customisation project and would mean they have to be ‘rewritten’ in the new project.

 

 

Graeme Laughton-Mutu | Focus Technology Group (NZ)

6 replies

A
Captain II
Forum|alt.badge.img+8
  • aiwan
  • Captain II
  • Answer
  • October 20, 2025

​@Graeme Laughton-Mutu 

 

Unfortunately, I believe you will have to extract the actions into a separate customisation project.

 

If they are in compiled .dll’s this makes it easier as you can add the actions into a new project, with no-code actions, the logic for these is usually contained within the customisation project and would mean they have to be ‘rewritten’ in the new project.

 

 

Aleks
Graeme Laughton-Mutu
Chris Hackett
dcomerford
Captain II
Forum|alt.badge.img+15
  • dcomerford
  • Captain II
  • October 20, 2025

​@Graeme Laughton-Mutu As ​@aiwan says no. If multiple packages are adding actions to the same screen then only the actions in the package with the highest priority will be added. 

Dermot Comerford
Graeme Laughton-Mutu
Chris Hackett
Graeme Laughton-Mutu
Semi-Pro I
Forum|alt.badge.img+1

​@Graeme Laughton-Mutu 

 

Unfortunately, I believe you will have to extract the actions into a separate customisation project.

 

If they are in compiled .dll’s this makes it easier as you can add the actions into a new project, with no-code actions, the logic for these is usually contained within the customisation project and would mean they have to be ‘rewritten’ in the new project.

 

 

Thanks for confirming my suspicions, thought it was worth asking just in case there was a known workaround or trick to get the publish process to pull each Action from different project and add them all to the screen.

For my example, I will migrate the Action from Project 1 to Project 2 so they are both there and are both added to the screen. 

Graeme Laughton-Mutu | Focus Technology Group (NZ)
A
Captain II
Forum|alt.badge.img+8
  • aiwan
  • Captain II
  • October 20, 2025

Thanks for confirming my suspicions, thought it was worth asking just in case there was a known workaround or trick to get the publish process to pull each Action from different project and add them all to the screen.

For my example, I will migrate the Action from Project 1 to Project 2 so they are both there and are both added to the screen. 

You could try to extract the actions from one .xml file and paste into the other, although I haven’t tried this and do not know if it would work...

Aleks
Graeme Laughton-Mutu
Graeme Laughton-Mutu
Semi-Pro I
Forum|alt.badge.img+1

Thanks for confirming my suspicions, thought it was worth asking just in case there was a known workaround or trick to get the publish process to pull each Action from different project and add them all to the screen.

For my example, I will migrate the Action from Project 1 to Project 2 so they are both there and are both added to the screen. 

You could try to extract the actions from one .xml file and paste into the other, although I haven’t tried this and do not know if it would work...

In theory that would work if placed in the right part of the .xml file for editing that screen, but in my case, it was quick and easy to add the one additional Action using the no-code project editor UI.

Going forward, I will be mindful that my customisations, and those of third parties/ISV’s will need to be checked for clashing Actions on screens to ensure they are all moved to a single project, so that they all are added to the screen.

Graeme Laughton-Mutu | Focus Technology Group (NZ)
A
Captain II
Forum|alt.badge.img+8
  • aiwan
  • Captain II
  • October 20, 2025

Sounds like a good idea!

 

I believe this only affects actions added via the customisation editor. Compiled actions seem not to be affected by this.

Aleks
Graeme Laughton-Mutu
Chris Hackett
Terms & ConditionsCookie settingsAccessibility statement
About Acumatica ERP system
Acumatica Cloud ERP provides the best business management solution for transforming your company to thrive in the new digital economy. Built on a future-proof platform with open architecture for rapid integrations, scalability, and ease of use, Acumatica delivers unparalleled value to small and midmarket organizations. Connected Business. Delivered.
© 2008 — 2024  Acumatica, Inc. All rights reserved