I was working on a layer today, and its pulling a nasty trick on me. None of the pages or layouts can be seen in application studio. But when I run the preview, it works great.
I’ve attached my layer.
MetaUIs(2).zip (5.8 KB)
Base application for The Company column is not valid. does not exist. Layers cannot be imported without base application.
I opened it up, and had to change the company to import. 
It shows the application map as blank. It does however preview.
Nice looking screen lol.
Its not done yet okay 
No I was serious, mine look like 
Running into a similar problem with 2025.2.3
If I take a classic dashboard and generate an application it will create the kinetic application with a blank company. I can add a layer.
When I export then import to another environment it states the company is blank and cannot import the layer.
Now prior to the upgrade this was working fine. It would create the application with a blank company but I could add a layer export it and then import it to another environment.
I had to import the base layer by itself then the custom layer. (And set it to all companies).
Then import the layer yet again without setting it to all companies.
Rather than both at once like I have been doing for 4 months.
2025.2.3 - also getting this error importing a layer that does have a base application… Order Entry.
It’s worse than I thought… Import is a broken mess. 5 years of Kinetic and always hoping they iron out major issues like this before delivering to customers. Pure fantasy.
Repro:
Tried on multiple cloud environments that are 2025.2 - same result.
On a separate note, Epicor calls GetApplications twice on every load of App Studio. 6MB+ of transfer each time, takes 5s+ per call on additional environments (faster processing on prod, but STILL) - grid doesn’t load until both calls complete.
At this rate, we pay Epicor to test their software for them. I imagine this will be fixed by the time it goes to live environments but seriously… paying them to test their software.
edited repro into a list for clarity.
Thanks for documenting this.
I had the same problem today. Import was barfed. If I used a solution it worked.
Blank page if I replaced the draft with a previous version it fixed it.
Nice Simon, maybe a solution is the way to go.
I was about to test that today! This helps.
Nope sadly, used a solution to move from one environment to another and it move, but opening app studio on the destination system blank page 
Funny, solution contained multiple layers for different apps, but only a few were effected
There is a PRB for this one and is slated for 2025.2.4.
Another hair-pulling issue making app studio nearly useless for me at this time:
Basic layer importing is a core issue.
Every tine I login to this forum I keep thinking that Classic has to be allowed to limp on a little longer.
I have 30 dashboards left to uplift, I can’t be doing the Curly shuffle (much as I would like to) for each one.
I have seen this recently, but I am manually editing my json. This will happen if the json is no longer “valid” for App Studio (still ran). Not saying that is the only reason, but this was my reason.
If you use Solution Workbench as suggested by Simon, this should hopefully resolve until 2025.2.4 is released.
The solution to my other layer issue has to do with company-specific layers, apparently. If you make a layer All Companies, it should not be affected. Epicor is unable to repro but I can across multiple separate installations / tenants, including a brand new configuration on cloud.
edit: Epicor does have a PRB on both. LMK if needed.
Mistype! Thank you!
Tested 2025.2.4… beware import broken via App Studio in a different concerning way.
It will say “Import Successful” but the layer is nowhere to be found!
Company specific layers are still problematic (CreateVersion still fails silently) and any attempt to export and re-import will not work. It will throw an error if you attempt to re-import as All Companies when a company specific layer exists - this is intentional, not sure why, but the error is highly specific not to be - but if you delete the layer from the company and import as all companies… poof.
