It looks like the CallCheckForNeedsLotAttrs event also opens the app … have you run a trace to see which one is actually running?
Also/Or, the name “IterativeEvent” makes me think that it’s called by name from something like a dataview-condition event widget - maybe that’s not being handled correctly, and the calling event has to be updated to use your custom event 
Haven’t been paying attention too much, so not sure if it’s warranted, but you most certainly can.
However, remember to absolutely do safe error checking in this BO.
The initial event is when the onclick tool save is clicked.
I think I may have to go up the tree of events until I find the right one to replace.
the big parent I believe is UpdateOverride
the Iterative event is triggered afterwards by a dataview-condition.
after that it runs an event I put in before the CallchkforneedslotattrsUpd
the app-open event seems to come from the dataview-condition, “checklotattrs_iterativeEvent”
If i can’t override that event, Do i need to override the dataview condition as well?
That’s what I’m unsure of - I think it would be worth the effort to try: Copy the event with the dataview-condition and change the trigger to override the original, then change the one field in the dataview-condition to explicitly call your override of the checkLotAttrs_iterativeEvent.
The iterative event is being called by updateoverride. Making changes to that one seems overkill and not something we want to touch.
Unless there is a better way I may have to end this endeavor. The override hook doesn’t seem to want to work in my verison.
It isn’t an option and it is something I’ve tried to manually enter into the hook box.
If you know for a fact that the event has not already been overridden … then I don’t have any other ideas to try.
I don’t believe that it is being overridden somewhere else.
I can’t confirm the override hook even works though. the Slide out is such a nested behavior and I’m unsure how else to handle.
Could I slip a before event on a iterative even and stop it somehow to call my own? some sort of manual override?
I’ve been having issues trying to insert something before that iterative event
That might work! with an Exit or Cancel at the end … but that might also mess with any other events that follow in the flow
I would check the trace to see what follows that might get cancelled
Here are two other methods we were just discussing on a different post yesterday. This is what was possible before they gave us the override option.
Lot Entry is called from a few screens Receiving, Customer Shipment Entry, Container receipt and maybe a few more.
With classic you could call it under the processes section with the customization and it would call the custom form from any calling screen that used Lot entry.
Can we not do something similar in Kinetic?
At first glance it looks like you can but it doesn’t actually seem to do anything.
You can pick the program and layer but when time comes to call the lot screen it just brings up the base layer not the published layer that you picked. Hmmm
Setting the Kinetic Enabled check box doesn’t seem to affect the outcome either.
And weirder it seems to create the menu option twice, with some random sequence number that I never put in
Well son of a -b- it is now working and not sure why
Positive I shut it down many times and didn’t work.
But my menu item is invoking the lot layer for Receipt Entry (I have not modified the events for receipt entry)
And oddly now it is no longer working. I have not worked on the customization of the layer or the menu option in the meantime.
There have been a few version changes to Kinetic since then.
This is one of the few times that I wish that I could edit the base layer. My customization consists of changing the labels on 2 of the text fields.
Or just a setting in Epicor, what Lot layer to call from receiving, and from shipping. That would be nice.
In 2025.1,the app open widget will not load the specificed custom layer in the client, but it still works in the browser. Been begging and pleading for support to submit this to PD for weeks now but you know how that goes. I have not been able to identify any workaround so far.
I’ve been playing with some code posted by klincecum, thank you Kevin!
This seems to work
Place a Pre-Processing Directive on Simple Service Ice.Lib.MetaFX.GetApp - credit to klincecum
if(request.id == “Erp.UI.LotNumberAttributesEntry”)
{
string layerName = “P001”;
List layers = request.properties.layers.ToList(); layers.Add(layerName);
request.properties.layers = layers.ToArray();
}
// Some caveats - in the thread it mentions that this will now call that layer whenever you call the program, even application studio and they recommend the following. I have not tested the following out
if (request.id == “Erp.UI.LotNumberAttributesEntry” && request.properties.mode != “AppStudio” && request.properties.additionalContext.ContainsKey(“menuId”))
