Is this expected behavior for an Precendence Constraint that uses an expression?

Question

I recently discovered expressioin precedence constraints, but they are not working the way I would expect. The expression part works, it is the after flow. What I have is a SQL Task that "exits" with 2 precendence constraints, this is level 1. One constraint checks if the variable is 0, the other NOT 0. Those 2 constraints flow to separate SQL Tasks (Level 2) that do something. Both of these tasks resolve to a single SQL Task (Level 3) that does some cleanup. What happens is that the process gets to level 2 and then exits with what appears a normal exit status even though level 3 is never executed. The work around is to duplicate the level 3 task for both streams but that seems unnecessary. Is there some setting I can use to resolve this. A picture is worh a 1000 but I am unable to insert. Sorry.

Answer 1

The question is on your precedence constraints that enter the level 3 task did you change the default of ANDing constraints to ORing, since this is what you want.  If you did not then the execution is as expected since only one of the 2 constraints entering level 3 is "executing".  Try changing the constraints to the level 3 task to OR and see if you get the behaviour you want.

HTH,
Matt

---

This posting is provided "AS IS" with no warranties, and confers no rights.

Answer 2

Matt,

Thanks that was it. Sorry for the delay in responding, not sure if it is this new forum software (my guess) or slow internet but I never received a notice that you had responded.