Kinetic 2023.2.5 on-prem
I’m working in Part Entry, and I’ve got a button configured that does a function call, returns a value, and I’m assigning that to a UD field on the Part table. I’ve got a row-update as the last step in the button click event. I don’t necessarily want this to invoke a save at that point - the user could be in the middle of a larger update, and they don’t need to click this button, have the update attempt and get error messages that required fields aren’t yet filled in when they’re in the midst of filling out the form. So, I’d just like the row-update to update the field and mark the row as dirty.
When I run this in the browser version - it works as expected. If I pull up a part record, click the button, I see the field properly populated. If I move around and do other things, and do something like go to the Part Plant tab where Epicor normally does a save for you - everything works great. If that was the ONLY change that I made and I go back to the landing page, I get a “Do you want to save the changes” just as I would expect.
However, if I run on the client and this was the only change I make, it’s as if it’s not recognizing the dirty row. If I go back to the landing page WITHOUT clicking save, it just discards that change. It’s as if it’s not recognizing the dirty row.
I realize the simple answer is to use the browser version. But shouldn’t the row-update event mark this as a dirty row? Is there another means to do this that I could add to the event, other than going through the process to commit that change to the database (which, I believe, is calling the Part.Update rest service)?
Thanks.
Kevin