Sanity check for Kinetic row-update

I’m working on two different cloud systems, and in one the established pattern I’ve used for the row-update widget, with an expression that substitutes for empty strings, isn’t working.

The console says the expression has evaluated correctly, but the row doesn’t update.

As an example, “{actionResult.output}” successfully updates the row IF there’s a value returned. If not, the field is literally set to {actionResult.output}. But if I use a conditional expression that evaluates to either the result or a default value, the field doesn’t change at all.

Has a recent update changed that behaviour?

1 Like

I haven’t seen anything like that, where the unevaluated value “{actionResult.output}” is returned, but the evaluated output is returned if present. I’ve seen some serious inconsistency in App Studio lately. I would probably start by creating an entirely new event from scratch and seeing if the new event behaves the same way.

It would save time if I could be confident that problems were definitely my fault …

App Studio is less inconsistent than it was, I’d like to stress, in the hopes it doesn’t punish me for implying otherwise.

1 Like