I have a constraint that works fine. When I move it to a warning I get nothing. I have seen it work on a GeoPoint but trying on a date just nothing happens in Connect.
What am I missing?
.>date(decimal-date-time(now()) - 7)
Calibration has been over 7 days, please calibrate asap and be critical of very high or low values
Also tried a radio button and again no warning appears.
Solved! Go to Solution.
I cannot seem to get warnings to work for any field. Has anyone got these to work? How should they work?
I was hoping warning was like a constraint but they can move on if they need to. In the past I have just been using Note fields for this but a warning would be much slicker. The word Esri in the binding makes me wonder if this is for something else. When I search on it I get so many hits I cannot find anything.
I have a calibration date that must be within one year of the of the inspection date. For the calibration date attribute, in the constraint cell, I have this - (today() - . < (1000*24*60*60*365)) with the constraint message being, "Odormeter Calibration Date is >1 Year. Odormeter must be recalibrated before reading can be submitted."
@DougBrowning, I have also needed soft constraints or warnings for non-geopoint questions. Since the bind::esri:warning field doesn't work in these instances, I created a workaround: follow the target question with a "note" type question containing the warning text that you want (I made the text red) and put your constraint logic in the "relevant" field for the note. If the constraint condition is met the note field will appear with your warning text.