App Studio - System Locked Event

Hey! I am having an issue with a system event in application studio. The event is marked as “locked”, but it has been overriden. Is there a way to revert it back to its original state without creating a new layer? I have been working on that layer for hours and the picking process is now broken …

Fulfillment Workbench - App Studio Base Event

When closing the event, I pressed “Yes” without paying attention. I had not changed anything as it is a locked event.

After save, Epicor has removed a huge part of the base event :

I found a solution. In case it happens to one of you, here’s how:

  1. Rerun the MetaUIConversion task in the Conversion Workbench.
  2. Once the task is completed (if error try to run it again), open your layer in app studio.
  3. Warnings may be displayed. Click on each event that has a warning event.
  4. The system events will display “Modified” instead of “Locked”. You can revert it back by clicking on the revert arrow icon in the right panel (see image below).

Our version is 2022.1.7. I hope it will be resolved in a future release as it seems to happen frequently.

3 Likes

Hey @vingeance,

I have an MES menu that was modified by a consultant when we were first launching Epicor. I noticed his modification is showing something similar to what you have posted here.

Here’s what I’m seeing:

What will happen if I choose to revert here?

This base event has the “Modified” tag. Reverting that event will reset the code to how Epicor natively coded it. The tag will now show “Locked” and the event be read-only. The “Disabled” checkbox in the top right corner will disappear.

I strongly recommend reverting all your “corrupted” base events back to base, to avoid unexpected application behavior.

The good news is Epicor fixed the issue in release 2023.1 - PRB0262240 (Application Studio Events corrupted when reopened).

Wouldn’t doing this possibly cause issues with layers that we’ve created?

Thanks for the response.

If your consultant accidentally modified base events in a layer (due to the bug mentioned here), then you should revert these events. The customizations he wanted to do / did in the layer will remain intact.

Otherwise, if your consultant deliberately modified base events in a layer, then you should reach out to him. It’s not a feature, it’s a bug :sweat_smile:

1 Like

Thank you, I appreciate it. :laughing: