New Bug Encountered: Expression Assistant evaluates workflow condition based on wrong context

I’m trying to use [_THISROW_BEFORE] in a workflow ‘only if this condition is true’ formula. When I reference columns in the workflow’s table, the assistant recognizes them as expected. However, as soon as I add [_THISROW_BEFORE].[ColumnName], the assistant says it’s not able to find the column AND suggests a column FROM ANOTHER TABLE. Then I tried referencing a column from that other table and the assistant accepted it, despite the column not existing in the workflow’s table.

It seems that adding [_THISROW_BEFORE] is changing the assistant’s context. My workflow is based on the Proof table, but adding [_THISROW_BEFORE] suddenly changes the assistant’s context to the parent Order table. Columns that were valid before are no longer recognized, and columns that don’t exist in the table are somehow found anyway.

bug video

Hi, could you give us the names of the affected app and workflow so that we can investigate? Also, what are the names of the correct table for the workflow, and the wrong table that the expression builder references?

Hi Harry,

It seems to be resolved now. I ran a similar test in another app earlier and the bug showed the same behavior, so it wasn’t limited to one app. I tested it again about 30 minutes ago, and now it works normally in both apps.