At a record level for the related action, is there a way to capture who is actua

@mjmallet To the best of my knowledge, the problem lies with the local!productInfo and local!projectInfo variables.

The problem here is, the local variables has the capacity to accept any type value, and because of this capability, the local variables hold values of type multiple especially when we make queries(also the query rules always return in array mode). For example, local!productInfo could look to us like it carries the result of type single. But what actually happens here is, the local variable carries the results of array type.

Now we might wonder why the problem comes with a variable that carries a results in an array mode. So, when we use these kind of variables in if condition, and function, or function etc, you will experience a weird behaviour which finally leads to such a state that the related action won't work even if you properly write a expression rule that results in true or false.

@mjmallet To the best of my knowledge, the problem lies with the local!productInfo and local!projectInfo variables.

The problem here is, the local variables has the capacity to accept any type value, and because of this capability, the local variables hold values of type multiple especially when we make queries(also the query rules always return in array mode). For example, local!productInfo could look to us like it carries the result of type single. But what actually happens here is, the local variable carries the results of array type.

Now we might wonder why the problem comes with a variable that carries a results in an array mode. So, when we use these kind of variables in if condition, and function, or function etc, you will experience a weird behaviour which finally leads to such a state that the related action won't work even if you properly write a expression rule that results in true or false.