Application Studio - Duplicated Order Entry Layer

Application studio is showing 2 rows of our ‘Global’ Order Entry layer.

My first thought was to see if there was any difference between the two. Turns out that you cannot select them individually. Export also seemed to only contain a single Global.json file.

As the name implies the layer was designed for ‘global’ use. Not sure why ESAPCO in the company column is present.

This being LIVE the curiousity of what would happen if I export, delete, and reimport the layer is outweighed by thoughts of pain and suffering. Off to PILOT with the intention to break things.

Wondering if anyone else has encountered this before?

Second to last column is a Company ID I believe.

In my application studio I have a base layer, and a single published layer on top of that. In my published layer it shows a weird company name that is not our name (but does include our site ID). I assume this is a temporary account Epicor used during some transition. In the application studio grid view, turn on the status column by going to the vertical … and choosing personalize columns, and check off any that aren’t showing. Does this give you any more information?

I know back in the day you could save a dashboard per company. May that is the same for a layer.

Status was the only missing column but no additional information presented itself. Thanks for the suggestion!

In our scenario ESAPCO as a Company ID would be an expected value if the layer wasnt built to be universally applied.

Yes, you can have company specific layers.

Good to know. Prior to this issue I was only aware of Menu Maint. company controls along with the usual customization (layer) selection shown below.

While trying to duplicate the ‘Global’ layer in our testing environments it did seem to show that both Layers and Personalizations can be company specific. Thanks for the callout @knash !

No luck replicating the duplication yet.

Following up on this post after a pleasant EpiCare experience. Epi rep responded with the below.

What is being reported can be broken down, as follows:

1. One Kinetic Customization was setup for All Companies (Blank Company Filed), while the other was for a Specific Company

2. This was how “Classic” Customizations functions.

3. So, in Kinetic 2025.2, I believe, Development Enhanced the Application Studio “Menu” Import process - to allow a Imported Kinetic Customization to be setup for a Specific Company, which is the “Default”

4. Because Solution Workbench uses the Application Import/Export features, Solution Workbench was also enhance - to match the Import Enhancements made to the Application Studio Menu. And again, the Default Import setting is to flag the custom items for the Company you are in

NOTE: In 2026.100.11, the Application Studio Menu’s Import Process has been enhanced, so now the Default Import option is set to All Companies.

5. And when one of the Kinetic Customizations is selected, both will be selected. I have seen this issue multiple times, but so far, I have Not been able to recreate - which is needed in order for Development to Find/Fix the reported issue.

6. And the only way to remove one of the Customizations, so that you can work on the other Customization, would be via a Data Fix. This DF is called OF_Del_UD0_TASK0999813.df

Please provide the following:

1. Attach a New Application Studio Menu screen shot, showing just the 2 Kinetic Customizations, and highlight the one you would like the DF to Delete.

2. Run a BAQ for xxxDef and Select the Kinetic Customization you want deleted. Then provide the following information for that record:

Company TableName SysRowID

Many of us have too, I’m sure we can figure out the steps.

Did you delete the layer to fix it? or go through the datafix?

I think @aosemwengie1 knows.

Export. Delete. Import. Every time.

Makes sense and beats waiting on a datafix. When I originally authored the issue it was only found in LIVE and I was scared to just FAFO.

Thinking outloud we now have EOM so I should be able to give it a dry run before going this route as well.