<?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>topic CSV coded value choice lists for view layers in ArcGIS Field Maps Questions</title>
    <link>https://community.esri.com/t5/arcgis-field-maps-questions/csv-coded-value-choice-lists-for-view-layers/m-p/1243485#M5079</link>
    <description>&lt;P&gt;As many of you know managing feature layer domains is a major time suck and tedious if you stick with a supported work flow.&amp;nbsp; You can spend hours populating and organizing coded values using the AGOL UI.&amp;nbsp; We have to maintain lists of pesticide applicators for ten or more contract crews that collect pesticide application data using Field Maps.&amp;nbsp; So you can imagine how excited I was when ESRI announced that choice lists can be managed via the Field Maps web app form builder by uploading a CSV.&amp;nbsp; I optimistically assumed that this improvement was about to eliminate our domain management issues.&amp;nbsp; I was dismayed when I learned that choice lists can not be managed for view layers and can only be applied to hosted feature layers.&amp;nbsp; We exclusively use view layers for field data collection to limit what features can be added, deleted and updated by field users.&amp;nbsp; After further investigation I found that editing the choice list in the Field Maps Web app actually modifies the field's coded value domain.&amp;nbsp; This was surprising since Field Maps form elements and associated settings are stored as part of the Web Map (as far as I am aware). This important fact is omitted from the documentation.&amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;It would be great if choice lists (and the coded value domain) could be managed for view layers.&amp;nbsp; It wouldn't be as odd as modifying the source data's domains since you can maintain different coded values for view layers already.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 22 Dec 2022 23:41:27 GMT</pubDate>
    <dc:creator>JCooley_ClackamasSWCD</dc:creator>
    <dc:date>2022-12-22T23:41:27Z</dc:date>
    <item>
      <title>CSV coded value choice lists for view layers</title>
      <link>https://community.esri.com/t5/arcgis-field-maps-questions/csv-coded-value-choice-lists-for-view-layers/m-p/1243485#M5079</link>
      <description>&lt;P&gt;As many of you know managing feature layer domains is a major time suck and tedious if you stick with a supported work flow.&amp;nbsp; You can spend hours populating and organizing coded values using the AGOL UI.&amp;nbsp; We have to maintain lists of pesticide applicators for ten or more contract crews that collect pesticide application data using Field Maps.&amp;nbsp; So you can imagine how excited I was when ESRI announced that choice lists can be managed via the Field Maps web app form builder by uploading a CSV.&amp;nbsp; I optimistically assumed that this improvement was about to eliminate our domain management issues.&amp;nbsp; I was dismayed when I learned that choice lists can not be managed for view layers and can only be applied to hosted feature layers.&amp;nbsp; We exclusively use view layers for field data collection to limit what features can be added, deleted and updated by field users.&amp;nbsp; After further investigation I found that editing the choice list in the Field Maps Web app actually modifies the field's coded value domain.&amp;nbsp; This was surprising since Field Maps form elements and associated settings are stored as part of the Web Map (as far as I am aware). This important fact is omitted from the documentation.&amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;It would be great if choice lists (and the coded value domain) could be managed for view layers.&amp;nbsp; It wouldn't be as odd as modifying the source data's domains since you can maintain different coded values for view layers already.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Dec 2022 23:41:27 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-field-maps-questions/csv-coded-value-choice-lists-for-view-layers/m-p/1243485#M5079</guid>
      <dc:creator>JCooley_ClackamasSWCD</dc:creator>
      <dc:date>2022-12-22T23:41:27Z</dc:date>
    </item>
    <item>
      <title>Re: CSV coded value choice lists for view layers</title>
      <link>https://community.esri.com/t5/arcgis-field-maps-questions/csv-coded-value-choice-lists-for-view-layers/m-p/1244023#M5088</link>
      <description>&lt;P&gt;I started using python code from &lt;A href="https://community.esri.com/t5/arcgis-online-questions/sort-coded-value-domains-arcgis-online/td-p/674424" target="_self"&gt;here&lt;/A&gt; to update/change my Domains on hosted feauture layers.&amp;nbsp; Works well, and lets me pick the order of the domains in the drop downs.&lt;/P&gt;&lt;P&gt;I run it from a Notebook to make it easy.&amp;nbsp; Just copy/paste the "new" domain list (update_dict) in the order I want into the update_dict cell, then run.&amp;nbsp; Will completely replace the domain for the field specifiec with the new list.&lt;/P&gt;&lt;P&gt;I maintain a separate notebook for each field I have Domains on to make it easy.&lt;/P&gt;&lt;P&gt;Also, not sure if it would break anything, and would need to test, but it appears as if you can change the domains for a hosted feature layer and any views of that layer independantly.&lt;/P&gt;&lt;P&gt;R_&lt;/P&gt;</description>
      <pubDate>Wed, 28 Dec 2022 17:26:25 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-field-maps-questions/csv-coded-value-choice-lists-for-view-layers/m-p/1244023#M5088</guid>
      <dc:creator>RhettZufelt</dc:creator>
      <dc:date>2022-12-28T17:26:25Z</dc:date>
    </item>
  </channel>
</rss>

