Hi, I wonder how we can Override standard event and replace it with our own. I want to replace checkLotAttrs_IterativeEvent in Receipt Entry. So I can Use my Custom Layer for Part Lot Attribute. When I copy the standard event and change the trigger to Event → Before → checkLotAttrs_IterativeEvent, my copied event won’t be triggered. Or maybe is there any Form / Setting in epicor to change the default layer for every Form opened.
1 Like
I guess I’m a bit confused by what you’re asking.
Are you asking how to override a base event or are you asking how to have a custom layer load as default?
If it’s the latter, then you just set that in Menu Maintenance.
If it’s the former, well, it’s possible, but complicated and you will need server access.
Example of me overriding the base ClearUI event:
Hi @hmwillett, when I try to update the layer from the menu maintenance it always returns this error “Update of global records not allowed”. What I’m doing right now is copying the menu to the current company and then I can Update the Customization layer. Sorry for not being clear, My question is for both maybe, because usually I always copy the standard event and then the parent standard event to change the standard event I intended to. And the ultimate goal for me to change the standard event is to change the app-open layer to use my custom layer. because I think in classic you can just change in the menu maintenance and it will change the form whenever you open it.
Generally, that’s the way to go for Kinetic apps. It’s not ideal, but it works.
This is the intended way to do this. Overriding the base app is a bit… hacky.
It functions this way in Kinetic as well so long as you can set it up properly in menu maint.
1 Like
@hmwillett oh so we still can override the standard event? is it in the meta UI folder? and how to set the menu maintenance properly in Kinetic is there another way without using the “copy to the current company” action?
I mean teeechnically yes… But it’s not pretty. A few custom jsonc files on the server, some customization workbench processes, and some magic which will get overwritten if you upgrade, so I mean–I can’t really recommend it. Copying the standard events upgrades nicely.
1 Like
hi @hmwillett, but the problem with copying the standard event is the event will be triggered twice. For example, the checkLotAttrs_IterativeEvent will be called from UpdateOverride Event when I copy the Event and set the trigger to After or Before UpdateOverride there will 2 events called, the standard and my copied event that makes the form I want to call from app-open will be opened twice. Because the problem is the standard event trigger is not from the button that I can just change the event, but from the event → before → update, until now I still figuring out what the solution for this.
Make a Before event on the one you want to “disable” and do this:
3 Likes