What are best practices on archiving layers in UI? Over time we have accumulated several old layers for screens, and is there a best practice on archiving these to reduce the # of layers seen when developing/deploying? Epicor version: 11.2.200.27
1 Like
I have a customer that had a really long list of old layers in Application Studio, and it started to slow us down when customizing or deploying. What worked best for us was creating a clear naming convention (like prefixing retired ones with zzz_ or suffixing with _old) so they’re pushed to the bottom of the layer list and easy to spot. That way, we keep them out of the way without immediately deleting anything we might need for reference later.
We also went into Menu Maintenance and unlinked any outdated layers from active menu IDs. Layers not tied to a menu won’t show up for end users, which helps keep things clean. If we were absolutely sure a layer was obsolete, we’d export it for backup and then delete it from Application Studio. That helped reduce clutter and made the dev environment a lot more manageable.
Hope that helps!
1 Like
You can’t rename a layer?
I should have clarified sorry, you have export the layer, create a new one with the desired naming convention, and import the contents. Currently on Kinetic 2024.1 using App Studio 2024.1
I’ve had too many layers corrupted just by exporting/importing them.