Forum Discussion

DanielJohnson2's avatar
DanielJohnson2
Qrew Trainee
4 years ago

Re: Pipelines Advanced Query

Another update:

I was on with support yesterday afternoon and we replicated the issue, which appears to be that you can't use the $prev language in an expression, which is unfortunate. Below is an example of the issue. In this case, we added the query expression in a conditional step because we weren't able to see the expression evaluate in the trigger. You can clearly see the condition is evaluating to true, even though the two values on either side of the equals sign are different. A = B is true?


Any ideas?


------------------------------
Daniel Johnson
------------------------------
  • DonLarson's avatar
    DonLarson
    Qrew Elite
    3 years ago
    Daniel,

    Did you ever resolve a way to do this?

    ------------------------------
    Don Larson
    ------------------------------
    • DanielJohnson2's avatar
      DanielJohnson2
      Qrew Trainee
      3 years ago

      Hey Don,

      I can't recall what the exact use case was here, but I'm now sure the issue was I was trying to evaluate a logical expression using a query expression. I'm sure if I used {% if a.$prev.status == a.status %}TRUE{% endif %} that the condition would have returned true if the values were actually equivalent, and false if they weren't. The query expression has to look like this: {'fid'.operator.'matching_value'}. Source



      ------------------------------
      Daniel Johnson
      ------------------------------