I have a updateable BAQ inside of a kinetic dashboard, its only job is to toggle a check box UD field. My grid pulls in the BAQ and updates the dataview, then to actually update the field I have a normal kinetic-baq update event followed by a baq get:
Any ideas what could be happening here? I thought maybe it was a dataview issue but my dataview seems to be fine. The payload also looks the exact same when it works vs when it doesn’t, so I’m pretty lost on what to look for
Rowmod is “U” for the changed row(s), null for an unchanged row
Network call looks fine to me, it’s successfully sending all of the rows in my dataview. The first call doesn’t successfully update the table, but the second one does. Maybe this is just an Epicor issue?
You might be able to call the same method called from BAQ Designer in app studio with kinetic-rest widget for a diagnostic test. you’d have to set up a new dataview with your (unchanged and changed) rows, with RowMod=“U” as appropriate, and set up that dataview in the request parameters to sendallrows.
Potential workarounds include using that kinetic-rest widget instead, or, chaining kinetic-rest(GetByID), row-update, kinetic-rest(Update) widgets in your event. Pull the record down, set rowmod U and checkbox true, push it back with update.
I’d open a bug on the indeterminate behavior - it should be consistent.
This seems like the case, yes it runs reliably when run in designer so guess it’s an issue with whatever funk is going on behind the scenes of the updatable dashboard kinetic-baq widget. I’ll open a bug on it, thank you!
