Survey123 Connect - Bind::ESRI::warning column

[AmandaBeck]

Can somebody please show me an example of how to use the bind::esri::warning column for a warning message on a geopoint question in Survey123 Connect? There are tons of examples out there for using constraints on a geopoint question - which I know how to implement - but I can't find a good example on a warning without having to use a note question type and the relevant column. 

From what I've read, you can use the same expressions you would in the Constraint column in the Warning column, however, when I try that nothing comes up as a warning in my survey after published. 

Any help would be great. 

Thanks!

[DougBrowning]

I have not tested it in a bit but here is how I use it for accuracy and it was working when I added it.

Add a hidden field called something like AccuracyMonumentCoord with a calculation of 

pulldata("@geopoint", ${GPSMonument}, "horizontalAccuracy")

Then on the geopoint question you do this.  Set the check in bind::esri:warning and the message if the check is true in bind::esri:warning_message

Hope that helps

[AmandaBeck]

Thanks for that @DougBrowning. However, I'm not sure that quite lines up with what I am trying to accomplish. 

What I need to do is have a geopoint question, where if a submitter creates a point outside a buffer I have on the basemap of the geopoint question, a warning shows telling them that their point is outside the buffer. 

I have a Constraint set up that performs this, but even if the point is outside the buffer, I still want submitters to be able to submit the survey. That's why I am looking into using the Warning columns. 

Do you know if that is possible - or if the Warning column is only for data point accuracy calculations like your example? 

[DougBrowning]

I think you can just move the constraint over to the bind::esri:warning column.  It just wants a true false then it shows the message.  

Are you maybe trying to put the pulldata inside the bind::esri:warning column?  That never seems to work.  You need any pulldata in a separate field then reference that in the bind::esri:warning column like I did above.