Skip to main content
Answer

Bug in customization editor merges two customizations when multiple windows open

  • May 21, 2025
  • 4 replies
  • 78 views

I have been encountering a major issue in 24R1.  When I open two different customizations in customization editor windows, the customization in the second window overwrites the customization in the first window (though the URL and name of the first customization window remain). 

Steps To Recreate:

  1. Create an empty customization called Test1 with no files or database scripts in it, and open it in a customization editor window. Leave open.
  2. Create a second customization called Test2 and add some database scripts and files to it. Open it in a second customization editor window while the first one is still open.
  3. In Test1 customization editor window, navigate away from (if needed) and back to the Database scripts section and/or the Files section.  You will see the scripts and files from customization Test2 duplicated in Test1.
  4. Most concerningly: In the Test1 editor window, delete one of the database scripts duplicated from Test2 and close the Test1 window.  Navigate away from and back to the database scripts section of Test2, see that the database script that you deleted from Test1 is now gone in Test2.

This happens on both Mac and Windows, in Firefox and in Chrome, recreated on multiple different sites.

Has anyone else encountered this before?  I was able to reliably recreate it, as was my coworker on his computer.  Perhaps this is a known issue, but when I try to go to the “Known Issues” portion of this site is just puts me on a generic landing page.

Best answer by DipakNilkanth

Hi ​@cnorten,

Yes, I’ve also encountered this behavior. It appears that when multiple customization editor windows are open at the same time, changes or content from one customization project can unintentionally affect another — exactly as you described. I was able to replicate this issue on my end as well.

To avoid potential data loss or unintentional overwrites, I would recommend working on one customization project at a time and avoiding multiple open editor windows.

It might be worth raising a support case with Acumatica directly if you haven't already. Hopefully, they can confirm if this is a known issue or provide a workaround/fix.

4 replies

DipakNilkanth
Pro III
Forum|alt.badge.img+13

Hi ​@cnorten,

Yes, I’ve also encountered this behavior. It appears that when multiple customization editor windows are open at the same time, changes or content from one customization project can unintentionally affect another — exactly as you described. I was able to replicate this issue on my end as well.

To avoid potential data loss or unintentional overwrites, I would recommend working on one customization project at a time and avoiding multiple open editor windows.

It might be worth raising a support case with Acumatica directly if you haven't already. Hopefully, they can confirm if this is a known issue or provide a workaround/fix.


dcomerford
Captain II
Forum|alt.badge.img+15
  • Captain II
  • May 22, 2025

@cnorten Same i have seen it will trying to look at two packages on same instance at same time.


darylbowman
Captain II
Forum|alt.badge.img+15

The key here is to always refresh the window of the package you are wanting to make changes to. If you open package A and then package B, when you try to make changes to package A, it will attempt to change package B, since that was the more recently loaded package. If you reload the package A window, changes can be made and saved successfully.

It’s kinda tricky to remember. I would recommend not working with multiple windows, but it is possible.


  • Author
  • Freshman I
  • May 22, 2025

Yeah, it’s pretty clear how to avoid the issue once you realize it is there.  Luckily I was on a staging site when I “discovered” it because I accidentally wiped out an entire customization.  We’re opening a ticket with Acumatica, as suggested.  Hopefully it has been (or will be) address in newer versions, because it’s a pretty major issue with really bad ramifications.