Yea i found log. But I dont understand why it finds as an issue since this field isnt updatable. This happens only if I send all rows. Took this line and updated as single and it worked. Even in classic there is no complains.
It seams somehow send all rows passes all decimals as a string I guess, but in payload object are passed as decimals without quotes
This worked great! Thank you.
I’ve noticed that when I convert an updatable dashboard it adds an update option but when I build one from scratch it does not so I found this post and now have a ghost icon that lets me update 
I have followed the instructions and I am able to update my date but when the refresh on the last trigger it brings in the complete baq instead of just the line that matches the sales order I am in. I tried to put information in the properties of the kinetic-baq get widget but then my data doesn’t update. Any suggestions?
very usefull
Thank you @hmwillett - very helpful!
I’m having an issue with this, hoping the brain trust may have some ideas.
I added a grid and form entity to Job Closing for capturing a job comment on the job header (CommentText). UBAQ works fine testing in BAQ editor, it’s firing off the update BAQ just fine, and updating the view as expected. But not committing the data.
Things I’ve double Checked
Any ideas?
Screenshots for context
View loaded via BAQ initial get triggered after getById into View “Comment”
Save button action
Do you have a data binding on that text field that you’ve added?
Bumping this one up a month + later as I still haven’t been able to figure out why it will not update.
A little refresher ..
Added a comments field and a UBAQ grid to the Job Closing form.
The BAQ has been tested in BAQ Studio and that part works fine.
However even though I’m not getting any errors the data is not being updated in App Studio.
Button Action
When testing via Chrome I can see the BAQ get called just fine
But I get an empty (but successful response)
Any other ideas?
Are you just updating the native Job Comments field from the JobHead? Is that not already part of the dataset that pulls the rest of the information, or is it not and that’s why you’re using a uBAQ?
Reason I ask, is because if it’s already part of the natively available dataset, you should be able to simply add it to your screen and when you click the page save icon it will write to that field, too.
I’m going to agree with @d_inman that this may be in the existing dataset and you don’t need a uBAQ to update it.
It’s unfortunately not part of the data set on jobclosing. Job Closing has its own little subset of the jobhead dataset.
Maybe try setting RowMod to “U”
What method are you updating in the BAQ? Custom directive or base?
Try setting rowmod = U like JB said.
How would I go about doing that in App studio, I don’t think I’ve done that before
