<?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 Allow Subtypes to Control Non-Nullable Property of Other Fields in Data Management Ideas</title>
    <link>https://community.esri.com/t5/data-management-ideas/allow-subtypes-to-control-non-nullable-property-of/idi-p/942213</link>
    <description>&lt;P&gt;Subtypes applied within a feature class or table provide a great range of options for enforcing data integrity by specifying the domains and/or default values to apply to other fields for each subtype. It would be very helpful to expand the field properties which can be controlled on a per-subtype basis to include the non-nullable/read-only property.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Suppose you have applied subtypes (0, 1, 2) to Column A, and Column B contains additional details that only apply when Column A equals 1 or 2. With this idea you could specify:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;For subtypes 1 and 2, Column B has a domain of "Column_B_Options"&lt;/LI&gt;&lt;LI&gt;For subtype 0, Column B default value is "N/A"&lt;/LI&gt;&lt;LI&gt;For subtype 0, Column B is read-only (so an editor couldn't erroneously enter a non-sequitur value)&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for considering my idea! Please upvote if you think it's worthwhile for Esri to take a look at.&lt;/P&gt;</description>
    <pubDate>Thu, 25 Aug 2022 23:05:28 GMT</pubDate>
    <dc:creator>MicahBabinski</dc:creator>
    <dc:date>2022-08-25T23:05:28Z</dc:date>
    <item>
      <title>Allow Subtypes to Control Non-Nullable Property of Other Fields</title>
      <link>https://community.esri.com/t5/data-management-ideas/allow-subtypes-to-control-non-nullable-property-of/idi-p/942213</link>
      <description>&lt;P&gt;Subtypes applied within a feature class or table provide a great range of options for enforcing data integrity by specifying the domains and/or default values to apply to other fields for each subtype. It would be very helpful to expand the field properties which can be controlled on a per-subtype basis to include the non-nullable/read-only property.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Suppose you have applied subtypes (0, 1, 2) to Column A, and Column B contains additional details that only apply when Column A equals 1 or 2. With this idea you could specify:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;For subtypes 1 and 2, Column B has a domain of "Column_B_Options"&lt;/LI&gt;&lt;LI&gt;For subtype 0, Column B default value is "N/A"&lt;/LI&gt;&lt;LI&gt;For subtype 0, Column B is read-only (so an editor couldn't erroneously enter a non-sequitur value)&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for considering my idea! Please upvote if you think it's worthwhile for Esri to take a look at.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Aug 2022 23:05:28 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/allow-subtypes-to-control-non-nullable-property-of/idi-p/942213</guid>
      <dc:creator>MicahBabinski</dc:creator>
      <dc:date>2022-08-25T23:05:28Z</dc:date>
    </item>
  </channel>
</rss>

