<?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 Create new domain type - Value domain in Data Management Ideas</title>
    <link>https://community.esri.com/t5/data-management-ideas/create-new-domain-type-value-domain/idi-p/962513</link>
    <description>&lt;P&gt;We use domains as valid value lists in editing environments to streamline editing for users when a list of values is required for a particular field. When codes/values are not needed the workflow is rather redundant to create a CODE &amp;amp; VALUE with the same exact values. If fact we started doing this more and more over the years since the use of coded values is inconsistent in the ArcGIS platform and also coded as XML in the GDB making back-end reporting and integration a pain. Today coded values domains are inconsistent and confusing for end-users where using functionality such as: queries, calculates, AGOL, Open Data, multi-version views.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;The coded/value domain is a redunant workflow and when only values are needed I propose the ability to create a value domain which is simply a list of values only. This will make it easier to manage and provide a consistant usage of a domain values across the platform for those that need it.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 25 Aug 2022 22:43:46 GMT</pubDate>
    <dc:creator>RonnieRichards</dc:creator>
    <dc:date>2022-08-25T22:43:46Z</dc:date>
    <item>
      <title>Create new domain type - Value domain</title>
      <link>https://community.esri.com/t5/data-management-ideas/create-new-domain-type-value-domain/idi-p/962513</link>
      <description>&lt;P&gt;We use domains as valid value lists in editing environments to streamline editing for users when a list of values is required for a particular field. When codes/values are not needed the workflow is rather redundant to create a CODE &amp;amp; VALUE with the same exact values. If fact we started doing this more and more over the years since the use of coded values is inconsistent in the ArcGIS platform and also coded as XML in the GDB making back-end reporting and integration a pain. Today coded values domains are inconsistent and confusing for end-users where using functionality such as: queries, calculates, AGOL, Open Data, multi-version views.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;The coded/value domain is a redunant workflow and when only values are needed I propose the ability to create a value domain which is simply a list of values only. This will make it easier to manage and provide a consistant usage of a domain values across the platform for those that need it.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 25 Aug 2022 22:43:46 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/create-new-domain-type-value-domain/idi-p/962513</guid>
      <dc:creator>RonnieRichards</dc:creator>
      <dc:date>2022-08-25T22:43:46Z</dc:date>
    </item>
    <item>
      <title>Re: Create new domain type - Value domain</title>
      <link>https://community.esri.com/t5/data-management-ideas/create-new-domain-type-value-domain/idc-p/962514#M1146</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;This is very timely, I've been doing exactly the same thing this week and grumbling to myself about the extra work involved. Thank you for taking the time to start the idea.&lt;BR /&gt;&lt;BR /&gt;FWIW, here's a thread looking for (faint hope) of alternate solutions:&lt;BR /&gt;&lt;A href="http://gis.stackexchange.com/questions/124203/feature-class-with-attribute-pick-lists-for-values-without-a-coded-value-domain"&gt;http://gis.stackexchange.com/questions/124203/feature-class-with-attribute-pick-lists-for-values-without-a-coded-value-domain&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Only alternate approach to date is to use a related Excel table for the Value domains, and do the editing there. Might work for some people in some circumstances.

&lt;!-- content transformation source ID: 00aE0000009EAdQ --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Dec 2014 17:53:55 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/create-new-domain-type-value-domain/idc-p/962514#M1146</guid>
      <dc:creator>mattwilkie</dc:creator>
      <dc:date>2014-12-03T17:53:55Z</dc:date>
    </item>
    <item>
      <title>Re: Create new domain type - Value domain</title>
      <link>https://community.esri.com/t5/data-management-ideas/create-new-domain-type-value-domain/idc-p/962515#M1147</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;I just make the code and value the same. It takes little time to create a table, add two columns, fill one in, dup with field calculator and create a domain from the table.

&lt;!-- content transformation source ID: 00aE0000009EE2O --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Dec 2014 07:40:11 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/create-new-domain-type-value-domain/idc-p/962515#M1147</guid>
      <dc:creator>RichardFairhurst</dc:creator>
      <dc:date>2014-12-04T07:40:11Z</dc:date>
    </item>
  </channel>
</rss>

