So I made an event in customer shipment entry that a user can press a button, and its supposed to follow the normal shipping route as if they were manually pressing buttons. Essentially compressing a few tasks into one. With the purpose of being to ship the job out, so it adds the lines using mass ship then ship all, then grabs the weight from our scale, then closes the packlist, freights it, and marks it as shipped.
It works great for a few packages, and then just freezes after freighting and sits there. You can scroll on the window still but can’t make any changes. My initial thought was maybe it took too long to freight and messed it up, so I added the 6 second timer after freight, but even then, nothing changed.
So for example upon freeze, I can scroll up and click the shipped checkbox, but nothing would actually change, the box would check but status wouldn’t switch from “Freighted” to “Shipped”.
Any ideas? In the second event that it calls, all its doing is clicking the shipped checkbox and then saving.
I’ve gone so far as to add a “Save and refresh” event after each step, just to make sure its always in sync but it did not like that even more, just broke at a few points.
When does it freeze? Use the dev console with debugging enabled to trace the events (F12 then CTRL + ALT + 8).
You’re probably either going to see it stop at an event that makes a network call (in which case, check the network tab to see which call is frozen) or you’re going to see 1000’s of events firing because there’s an unintended loop somewhere.
It seems like it freezes after I freight, and then when it clicks shipped is when it locks up. The status does not change to “Shipped” and if i close it and re-open that one, it is still freighted with shipped unchecked. I will try the console now and report back. Thank you!
No network issue, no 1000 events, but there is a difference, it looks like it’s hitting a conditional where %currentdataview% = shipdtl on the freeze, and its shiphead on the success. I’m not sure why that would differ or be changing, but there is an event in the fail that specifically calls it. After I call the getweight from scale function, it performs an update, which calls “CallCheckPCBinOutLocation”, and for some reason, during the short time after it calls that, but before it returns the request, it calls ViewChanging to ShipDtl, vs the successful one does not.
So after the weight step, I’m going to try Dataview-current-set to ShipHead, and maybe that will work?
