Hi, As you can see on the above screenshot, the quota for Cities is exceeded, although it is coded the same way as other quotas, which work as expected (flagging respondents as QuotaMet and ending their survey when the quota is met). For Cities, respondents are not flagged and they nothing happens even though the quota is exceeded. I suspect the issue comes from the fact that urbanity (Cities) is set using Javascript, by matching the respondent’s zipcode with the corresponding “urbanity” value using a .csv. However, I used the same method two years ago and I don’t remember having any issue with the quota.Any idea how to make this quota binding?Thanks in advance!

Yes. I think I’ve found the solution: when setting the condition, instead of “Is Equal to”, I need to use “contains”.It’s weird because I don’t see why the quota is incremented if the condition is not recognized as met, but this seems to solve the bug.

Just an idea...try setting the “urbanity” to itself in the survey flow after the JS runs:urbanity = ${e://Field/urbanity}

Quota (defined with embedded data) exceeds target

Quota (defined with embedded data) exceeds target | Experience Community

Sign up

Login to the Community

Scanning file for viruses.

This file cannot be downloaded