<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>idea Constraint evaluation for numbers during data entry in ArcGIS Survey123 Ideas</title>
    <link>https://community.esri.com/t5/arcgis-survey123-ideas/constraint-evaluation-for-numbers-during-data/idi-p/940939</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="background-color: #ffffff;"&gt;The idea is&amp;nbsp;for numerical fields to, instead of using a conventional constraint on&amp;nbsp;this field (that is only validated when the data is submitted), directly restrict the entry of data into this field, especially for the spinner appearance (let's call it "restricted spinner" appearance). E g. an integer that is constrained to values between 0 and 50.&amp;nbsp;When these limits are reached the spinner buttons just stop adding (plus button at 50) or subtracting (minus button at 0). This would be a much more direct user experience.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 27 Aug 2018 07:39:23 GMT</pubDate>
    <dc:creator>JürgenBiendara1</dc:creator>
    <dc:date>2018-08-27T07:39:23Z</dc:date>
    <item>
      <title>Constraint evaluation for numbers during data entry</title>
      <link>https://community.esri.com/t5/arcgis-survey123-ideas/constraint-evaluation-for-numbers-during-data/idi-p/940939</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="background-color: #ffffff;"&gt;The idea is&amp;nbsp;for numerical fields to, instead of using a conventional constraint on&amp;nbsp;this field (that is only validated when the data is submitted), directly restrict the entry of data into this field, especially for the spinner appearance (let's call it "restricted spinner" appearance). E g. an integer that is constrained to values between 0 and 50.&amp;nbsp;When these limits are reached the spinner buttons just stop adding (plus button at 50) or subtracting (minus button at 0). This would be a much more direct user experience.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Aug 2018 07:39:23 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-ideas/constraint-evaluation-for-numbers-during-data/idi-p/940939</guid>
      <dc:creator>JürgenBiendara1</dc:creator>
      <dc:date>2018-08-27T07:39:23Z</dc:date>
    </item>
    <item>
      <title>Re: Constraint evaluation for numbers during data entry</title>
      <link>https://community.esri.com/t5/arcgis-survey123-ideas/constraint-evaluation-for-numbers-during-data/idc-p/1241758#M2324</link>
      <description>&lt;P&gt;Is this why my spinner will still allow a user to iterate upwards despite me adding the constraint:&lt;/P&gt;&lt;P&gt;.&amp;gt;=1 and .&amp;lt;=${MAXCOUNT}&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;??&lt;/P&gt;</description>
      <pubDate>Thu, 15 Dec 2022 22:04:55 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-ideas/constraint-evaluation-for-numbers-during-data/idc-p/1241758#M2324</guid>
      <dc:creator>ahargreaves_FW</dc:creator>
      <dc:date>2022-12-15T22:04:55Z</dc:date>
    </item>
  </channel>
</rss>

