Ok, then instead of the getbyid, replace that with a set field widget
chose ds.HDCase and your ud field for specified field
choose updated row
and set it’s value in the expression
it should return in the dataset and display on screen
Ok, then instead of the getbyid, replace that with a set field widget
chose ds.HDCase and your ud field for specified field
choose updated row
and set it’s value in the expression
it should return in the dataset and display on screen
@klincecum thanks for your suggestion.
since it is updating in post-processing , the set by field is not having the effect.
@hkeric.wci your thoughts on the error.
What effect?
If you set the (correct) field in the dataset in post, it will be returned to the calling form.
If the screen does not reflect that, then the original programmer of the form did not program it to refresh from the returned dataset.
In that case, you will need to refresh the screen in client code, after the call is complete.
sorry , I meant to say the field is not updated.
can we refresh the ui post bpm?
Is this in Classic?
Kinetic
I’m surprised that either one is not updating after the call, but whatever, I’ve seen it before.
First thing I would do is bring up the dev console and on the network tab, find the return data for that bpm call.
Make sure it is returning properly. If it’s not, we should try to fix that first.
If it is returning properly, then you’ll have to do it yourself. You can figure out whatever event calls that bpm in kinetic, and add an event after that to update the field in the dataview for the form.