<?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 All Form Element properties should be dynamic in ArcGIS Field Maps Ideas</title>
    <link>https://community.esri.com/t5/arcgis-field-maps-ideas/all-form-element-properties-should-be-dynamic/idi-p/1180011</link>
    <description>&lt;P&gt;For each property of a form element (group or field) allow their values to accept expressions.&amp;nbsp; The exceptions to this rule would be the type, input type, fieldName properties.&amp;nbsp;&lt;/P&gt;&lt;P&gt;While inputType might be fixed, its sub properties might benefit from being dynamic (thinking of dynamic min/max length of a text-box as part of some validation).&lt;/P&gt;&lt;P&gt;The same considerations should be made when introducing new form element properties.&lt;/P&gt;&lt;P&gt;Type: Group&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;description&lt;UL&gt;&lt;LI&gt;Add descriptionExpression or allow inline with the description property&lt;UL class="lia-list-style-type-square"&gt;&lt;LI&gt;Same or Similar Arcade Profile as Form Calculation&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;label&lt;UL&gt;&lt;LI&gt;Add labelExpression&amp;nbsp;or allow inline with the label property&lt;UL class="lia-list-style-type-square"&gt;&lt;LI&gt;Same or Similar Arcade Profile as Form Calculation&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRIKE&gt;visibilityExpression&lt;/STRIKE&gt;&lt;UL class="lia-list-style-type-lower-alpha"&gt;&lt;LI&gt;Already Exists&lt;UL class="lia-list-style-type-square"&gt;&lt;LI&gt;Utilizes Constraint Profile (returns boolean)&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;initialState&amp;nbsp;&lt;UL&gt;&lt;LI&gt;Add initialStateExpression or allow inline with initialState property&lt;BR /&gt;&lt;UL class="lia-list-style-type-square"&gt;&lt;LI&gt;Must return "expanded" or "collapsed"&lt;/LI&gt;&lt;LI&gt;Or change the property name to "Expanded" and utilize the constraint profile.&lt;/LI&gt;&lt;LI&gt;Use Case:&amp;nbsp; If all values in a group are complete, collapse the group and expand another&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Type: Field&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;description&lt;UL&gt;&lt;LI&gt;Add descriptionExpression or allow inline with the description property&lt;UL class="lia-list-style-type-square"&gt;&lt;LI&gt;Same or Similar Arcade Profile as Form Calculation&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;label&lt;UL&gt;&lt;LI&gt;Add labelExpression or allow inline with the label property&lt;UL class="lia-list-style-type-square"&gt;&lt;LI&gt;Same or Similar Arcade Profile as Form Calculation&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRIKE&gt;editable&lt;/STRIKE&gt;&lt;UL&gt;&lt;LI&gt;Already Exists (See editableExpression)&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;hint&lt;UL&gt;&lt;LI&gt;Add hintExpression or allow inline with the hint property&lt;UL class="lia-list-style-type-square"&gt;&lt;LI&gt;Same or Similar Arcade Profile as Form Calculation&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRIKE&gt;editableExpression&lt;/STRIKE&gt;&lt;UL&gt;&lt;LI&gt;Already Exists&lt;UL class="lia-list-style-type-square"&gt;&lt;LI&gt;Utilizes Constraint Profile&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRIKE&gt;visibilityExpression&lt;/STRIKE&gt;&lt;UL&gt;&lt;LI&gt;Already Exists&lt;UL class="lia-list-style-type-square"&gt;&lt;LI&gt;Utilizes Constraint Profile&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRIKE&gt;requiredExpression&lt;/STRIKE&gt;&lt;UL&gt;&lt;LI&gt;Already Exists&lt;UL class="lia-list-style-type-square"&gt;&lt;LI&gt;Utilizes Constraint Profile&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRIKE&gt;valueExpression&lt;/STRIKE&gt;&lt;UL&gt;&lt;LI&gt;Already Exists&lt;UL class="lia-list-style-type-square"&gt;&lt;LI&gt;Utilizes Form Calculation Profile&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;In addtion, many of the expression could be simplified by accepting the {fieldName} notation that we are familiar with in the popup configuration.&amp;nbsp; This way we could string together the existing values of fields or develop a more dynamic expression with arcade.&lt;/P&gt;</description>
    <pubDate>Sat, 04 Jun 2022 16:49:48 GMT</pubDate>
    <dc:creator>JustinReynolds</dc:creator>
    <dc:date>2022-06-04T16:49:48Z</dc:date>
    <item>
      <title>All Form Element properties should be dynamic</title>
      <link>https://community.esri.com/t5/arcgis-field-maps-ideas/all-form-element-properties-should-be-dynamic/idi-p/1180011</link>
      <description>&lt;P&gt;For each property of a form element (group or field) allow their values to accept expressions.&amp;nbsp; The exceptions to this rule would be the type, input type, fieldName properties.&amp;nbsp;&lt;/P&gt;&lt;P&gt;While inputType might be fixed, its sub properties might benefit from being dynamic (thinking of dynamic min/max length of a text-box as part of some validation).&lt;/P&gt;&lt;P&gt;The same considerations should be made when introducing new form element properties.&lt;/P&gt;&lt;P&gt;Type: Group&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;description&lt;UL&gt;&lt;LI&gt;Add descriptionExpression or allow inline with the description property&lt;UL class="lia-list-style-type-square"&gt;&lt;LI&gt;Same or Similar Arcade Profile as Form Calculation&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;label&lt;UL&gt;&lt;LI&gt;Add labelExpression&amp;nbsp;or allow inline with the label property&lt;UL class="lia-list-style-type-square"&gt;&lt;LI&gt;Same or Similar Arcade Profile as Form Calculation&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRIKE&gt;visibilityExpression&lt;/STRIKE&gt;&lt;UL class="lia-list-style-type-lower-alpha"&gt;&lt;LI&gt;Already Exists&lt;UL class="lia-list-style-type-square"&gt;&lt;LI&gt;Utilizes Constraint Profile (returns boolean)&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;initialState&amp;nbsp;&lt;UL&gt;&lt;LI&gt;Add initialStateExpression or allow inline with initialState property&lt;BR /&gt;&lt;UL class="lia-list-style-type-square"&gt;&lt;LI&gt;Must return "expanded" or "collapsed"&lt;/LI&gt;&lt;LI&gt;Or change the property name to "Expanded" and utilize the constraint profile.&lt;/LI&gt;&lt;LI&gt;Use Case:&amp;nbsp; If all values in a group are complete, collapse the group and expand another&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Type: Field&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;description&lt;UL&gt;&lt;LI&gt;Add descriptionExpression or allow inline with the description property&lt;UL class="lia-list-style-type-square"&gt;&lt;LI&gt;Same or Similar Arcade Profile as Form Calculation&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;label&lt;UL&gt;&lt;LI&gt;Add labelExpression or allow inline with the label property&lt;UL class="lia-list-style-type-square"&gt;&lt;LI&gt;Same or Similar Arcade Profile as Form Calculation&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRIKE&gt;editable&lt;/STRIKE&gt;&lt;UL&gt;&lt;LI&gt;Already Exists (See editableExpression)&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;hint&lt;UL&gt;&lt;LI&gt;Add hintExpression or allow inline with the hint property&lt;UL class="lia-list-style-type-square"&gt;&lt;LI&gt;Same or Similar Arcade Profile as Form Calculation&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRIKE&gt;editableExpression&lt;/STRIKE&gt;&lt;UL&gt;&lt;LI&gt;Already Exists&lt;UL class="lia-list-style-type-square"&gt;&lt;LI&gt;Utilizes Constraint Profile&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRIKE&gt;visibilityExpression&lt;/STRIKE&gt;&lt;UL&gt;&lt;LI&gt;Already Exists&lt;UL class="lia-list-style-type-square"&gt;&lt;LI&gt;Utilizes Constraint Profile&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRIKE&gt;requiredExpression&lt;/STRIKE&gt;&lt;UL&gt;&lt;LI&gt;Already Exists&lt;UL class="lia-list-style-type-square"&gt;&lt;LI&gt;Utilizes Constraint Profile&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;STRIKE&gt;valueExpression&lt;/STRIKE&gt;&lt;UL&gt;&lt;LI&gt;Already Exists&lt;UL class="lia-list-style-type-square"&gt;&lt;LI&gt;Utilizes Form Calculation Profile&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;In addtion, many of the expression could be simplified by accepting the {fieldName} notation that we are familiar with in the popup configuration.&amp;nbsp; This way we could string together the existing values of fields or develop a more dynamic expression with arcade.&lt;/P&gt;</description>
      <pubDate>Sat, 04 Jun 2022 16:49:48 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-field-maps-ideas/all-form-element-properties-should-be-dynamic/idi-p/1180011</guid>
      <dc:creator>JustinReynolds</dc:creator>
      <dc:date>2022-06-04T16:49:48Z</dc:date>
    </item>
    <item>
      <title>Re: All Form Element properties should be dynamic</title>
      <link>https://community.esri.com/t5/arcgis-field-maps-ideas/all-form-element-properties-should-be-dynamic/idc-p/1253456#M1073</link>
      <description>&lt;P&gt;Would love for fields to accept dynamic expressions! I would use Field Maps much more if this was possible&lt;/P&gt;</description>
      <pubDate>Tue, 31 Jan 2023 18:08:01 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-field-maps-ideas/all-form-element-properties-should-be-dynamic/idc-p/1253456#M1073</guid>
      <dc:creator>SaranehFitzgeraldWP</dc:creator>
      <dc:date>2023-01-31T18:08:01Z</dc:date>
    </item>
    <item>
      <title>Re: All Form Element properties should be dynamic</title>
      <link>https://community.esri.com/t5/arcgis-field-maps-ideas/all-form-element-properties-should-be-dynamic/idc-p/1281847#M1182</link>
      <description>&lt;P&gt;Adding my support for this idea! The form title accepts dynamic labeling, I wish other field and group names did as well.&lt;/P&gt;&lt;P&gt;Use case being fields that serve a dual-purpose depending on AssetType.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Apr 2023 14:31:38 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-field-maps-ideas/all-form-element-properties-should-be-dynamic/idc-p/1281847#M1182</guid>
      <dc:creator>KPyne</dc:creator>
      <dc:date>2023-04-24T14:31:38Z</dc:date>
    </item>
  </channel>
</rss>

