I have an issue that EpicCare was not able to resolve to this point.
I created several App Studio customized layers in my Test Environment which tested successfully. I used Solution workbench to migrate them to my live environment.
In the live environment, not only did the New layers show up completely blank, but the BASE layers were also BLANK.
I had created one App Studio Kinetic Customization on the POEntry Layer in my Live Environment. This worked fine. Now, I moved this to the test Environment using Solution Workbench, and it did the same thing. Blank New layer, and the BASE PO Entry layer was BLANK.
Has anyone experienced this issue? I am not sure how to resolve this. I have run Conversion 191, Tried recreating new Solution Files, Tried the Export/Import of App Studio Layers to no avail.
This might not be relevant to your situation, but I find (in 2024.1 SaaS) that after installing a layer using the web version of Solution Workbench, I sometimes need to open the layer in Application Studio (and ignore how it looks) and click the “preview” icon at the top right (then close the preview page), then exit Application Studio. Using “preview” gets the server to “let go” of the old version of the layer that it is caching somewhere, and use the current version of the layer. (This occurs when a layer by that name already exists, where I am replacing it with a revised version of the layer that has the same name.)
Steve,
Thanks for the tip - unfortunately, that did not do the trick.
Speaking with EpicCare support, it seems to be something related to the inability of Conversion 191. That should rebuild the MetaUI tables which would rebuild the BASE layers if there is a problem.
Well, there is a problem. They are BLANK. However - rebuilding them does nothing. If I navigate to the folder location on the application server, files are there. However, my files are on the D: Drive on my server. Always have been. The default location is on the C:. This could be the issue.
If I understand correctly, when the conversion 191 runs, this updates the SQL server tables based on the files in the folders located in MetaUI folder. If this is looking for a hardcoded path to the C:.… path and not the D:\ That could be my issue. I am waiting for EpicCare to get back to me on a solution for this. Until then I am dead in the water.
Unless someone else has run into something similar. I do not know what I did make this happen.
I will update this with the solution when I get one. Until then - I am open to any and all suggestions.
There was an “incident” on 3/5/2025 where a bunch of cloud customers were affected… perhaps this was part of the “cause”??? Not sure, and they never said. But the dates line up! Maybe they were pushing out a hot fix?
But anyway… the Application Map is back in the base form:
