So I’ve added a window in MES that allows viewing and resolving production line exceptions. However I’ve run into a snag. After resolving an exception, on my grid in MES it shows complete but it appears to not be getting saved. (the other issue is why is it in my toolbar I have a save but it doesn’t show up) but all that aside.
I’ve taken a look at the ds data on the network call stack and it seems like on the update that my payload isn’t populating anything. just says ds{} and thus the response is reading empty. I also know for certain that I am getting an entry on my GetByID as it shows accurately in the response for the event call.
… and then, you’re immediately “updating” that dataset (sending the same dataset) back to the server.
Are you trying to alter any of the data prior to saving it back to the server (via Update method)?
Not sure I’m following what you’re trying to do. Perhaps I’m misinterpreting.
~*~
If its helpful, below is my set-up for a UD02 “Update”. (I would recommend deleting your existing Update call and starting from scratch. They get corrupted sometimes and hard to troubleshoot, so it may just be easier to delete it and start new.
Weelll, for anyone who runs into similar issues, i ended up making some adjustments. Switched my BAQ to just a UBAQ and used the kinetic baq update method. I did row-update for each field and then set my datafield selected row to RowMod = “U”. then did grid refresh and closed slideout