I have a working layer customization in our text environment. I went to copy it back into our production environment using export/import but found one of the event customizations come in wrong. I then did a simple “save as” staying in the test environment and it yields the exact mess up event. The working event looks like this.
A “save as” or export/import yields this. The Condition Shape Labels disappear, but worse yet, it creates duplicate widgets and creates different interconnects. I’ve tried to clean it up, but the underlying code that executes does not match what I’ve cleaned it up to be. I’ve created a case with Epicor, but they haven’t responded yet.,
Any events I have made with that level of complexity constantly corrupt at the slightest jostle. I’ll be very curious to see if you get anywhere with your case.
In the mean time, if you split it into many events, it should be less prone to evil behavior.
Pretty much what Evan said.I had a event similar to your with a bunch of stuff and it got corrupted. I learned to split events up using Event-Next so when a part gets corrupted it can be rebuilt easy.
I know this doesn’t help you now and I don’t have any suggestions that haven’t already been tried.
Could be wrong but last time i looked at the json, there’s no connectors collection to be found. in other words it’s just a nested array of actions. you cannot ensure an action will fire after another just because you drew a line between. theres no way for the json to model an action with two points of entry.
thats why it split at and duplicated your function.
the pretty diagram isnt doing what we think its doing. if you want to go the same place on two paths split event and call that place from both.
EDIT: so 3 events like this (orange arrows are event-next actions):
Thanks Josh. Appreciate the thoughtful detail. Sounds like waiting for Epicor to weigh in is a waste of time.
My overwhelming take away is this. My classic customization lived in only one place, in the client screen. Clean, easy to maintain and keep track of. With Kinetic, I had to use a BAQ, a Function, a couple data views and now a total of 7 events, 3 of which responsible for a single action. Stuff is all over the place. Going to be a challenge maintaining things as time goes on.
I’ve rebuild the event as suggested and it now works and can be exported reliably. The issue of the condition shape label not saving remains. Odd that in my original event they did stick and would show when reloaded. Is this a known problem with 2023.2?
I have no idea. Guessing it’s an artifact of the diagram layout and is saved in local layer and is completely ignored on export/import. Just a guess tho.
