I have a branch in my survey flow that checks the values of a NextRead and QNextRead embedded data variable. For testing purposes I simply set the branch logic to 'If NextRead is equal to 1 And QNextRead is equal to 1' then execute the stuff in the branch. I should note at this point that the NextRead value is coming from Contact embedded data and QNextRead originates from the querystring. When NextRead and QNextRead values are equal to 1 then this branch executes (below is a screenshot of the branch logic)However if I add an additional condition that compares the two ED variables, then the branch is false (does not execute). If both of the first two conditions are true, then why isn't the third?

Hi w.patrick.gale! I connected with our Support team on this one, as it definitely seemed a bit tricky. They let me know that you will need to use Piped Text in the third line of the branch (in the second screenshot) to make this work. "QNextRead is Equal to NextRead," is comparing the value of the QNextRead Embedded Data element (which is equal to 1) to the string "NextRead" instead of the value of the Embedded Data element called "NextRead." Instead of "NextRead" in the third line it should be the Piped Text "${e://Field/NextRead}." Here isa screenshotof what that would look like.

Thank you @LaurenK. It would be helpful if the support documentation would specify if a field will parse a plain variable name (in the case of the 'left' field for this condition) or when piped text is expected (in the case of the 'right' field for this condition). It is especially difficult to test this within the survey flow if it isn't clear to users what the fields will or will not parse.

Branching logic to compare embedded data variables is failing

Branching logic to compare embedded data variables is failing | Experience Community

Sign up

Login to the Community

Scanning file for viruses.

This file cannot be downloaded