<?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 Apply Relationship Class Rules to Collector in ArcGIS Enterprise Ideas</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-ideas/apply-relationship-class-rules-to-collector/idi-p/941539</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;I suggest enforcing &lt;A href="http://resources.arcgis.com/EN/HELP/MAIN/10.1/index.html#//004t00000004000000" target="_blank"&gt;relationship class rules&lt;/A&gt; to feature service and applying that to Collector.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;"&lt;SPAN style="color: rgb(77, 77, 77); font-family: arial,helvetica,sans-serif; font-size: 12.8px;"&gt;[...] HazMat landfill can be related to one or two deep wells or between two and seven shallow wells. However, if a sanitary landfill is related to a deep well, but no rule has been created between these two subtypes, the Validate Features command will consider the relationship to be invalid(&lt;/SPAN&gt;&lt;A href="http://resources.arcgis.com/EN/HELP/MAIN/10.1/index.html#//004t00000004000000)"&gt;http://resources.arcgis.com/EN/HELP/MAIN/10.1/index.html#//004t00000004000000)&lt;/A&gt;&lt;SPAN style="color: rgb(77, 77, 77); font-family: arial,helvetica,sans-serif; font-size: 12.8px;"&gt;"&lt;BR /&gt;&lt;BR /&gt;In above scenario, it'd be ideal if user selects HazMat in the origin table, only deep wells and shallow wells show as available choices in the destination table drop-down. Also, if the number exceeds the maximum limit, show a warning message to user. I suppose this can be a challenge for offline data collection.&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;

&lt;!-- content transformation source ID: 087E0000000kA6k --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 28 Oct 2015 12:56:06 GMT</pubDate>
    <dc:creator>AhjungKim4</dc:creator>
    <dc:date>2015-10-28T12:56:06Z</dc:date>
    <item>
      <title>Apply Relationship Class Rules to Collector</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-ideas/apply-relationship-class-rules-to-collector/idi-p/941539</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;I suggest enforcing &lt;A href="http://resources.arcgis.com/EN/HELP/MAIN/10.1/index.html#//004t00000004000000" target="_blank"&gt;relationship class rules&lt;/A&gt; to feature service and applying that to Collector.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;"&lt;SPAN style="color: rgb(77, 77, 77); font-family: arial,helvetica,sans-serif; font-size: 12.8px;"&gt;[...] HazMat landfill can be related to one or two deep wells or between two and seven shallow wells. However, if a sanitary landfill is related to a deep well, but no rule has been created between these two subtypes, the Validate Features command will consider the relationship to be invalid(&lt;/SPAN&gt;&lt;A href="http://resources.arcgis.com/EN/HELP/MAIN/10.1/index.html#//004t00000004000000)"&gt;http://resources.arcgis.com/EN/HELP/MAIN/10.1/index.html#//004t00000004000000)&lt;/A&gt;&lt;SPAN style="color: rgb(77, 77, 77); font-family: arial,helvetica,sans-serif; font-size: 12.8px;"&gt;"&lt;BR /&gt;&lt;BR /&gt;In above scenario, it'd be ideal if user selects HazMat in the origin table, only deep wells and shallow wells show as available choices in the destination table drop-down. Also, if the number exceeds the maximum limit, show a warning message to user. I suppose this can be a challenge for offline data collection.&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;

&lt;!-- content transformation source ID: 087E0000000kA6k --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Oct 2015 12:56:06 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-ideas/apply-relationship-class-rules-to-collector/idi-p/941539</guid>
      <dc:creator>AhjungKim4</dc:creator>
      <dc:date>2015-10-28T12:56:06Z</dc:date>
    </item>
    <item>
      <title>Re: Apply Relationship Class Rules to Collector</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-ideas/apply-relationship-class-rules-to-collector/idc-p/941540#M1059</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Excellent idea! This just came up for me at work. Why on Earth would someone downvote this idea???&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Apr 2019 16:06:39 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-ideas/apply-relationship-class-rules-to-collector/idc-p/941540#M1059</guid>
      <dc:creator>MicahBabinski</dc:creator>
      <dc:date>2019-04-26T16:06:39Z</dc:date>
    </item>
    <item>
      <title>Re: Apply Relationship Class Rules to Collector</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-ideas/apply-relationship-class-rules-to-collector/idc-p/941541#M1060</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;An Esri developer? Joking   &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ahjung&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Apr 2019 16:12:06 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-ideas/apply-relationship-class-rules-to-collector/idc-p/941541#M1060</guid>
      <dc:creator>AhjungKim4</dc:creator>
      <dc:date>2019-04-26T16:12:06Z</dc:date>
    </item>
    <item>
      <title>Re: Apply Relationship Class Rules to Collector</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-ideas/apply-relationship-class-rules-to-collector/idc-p/941542#M1061</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;H1 style="color: #000000; background: 0px 0px; border: 0px; font-size: 28px; margin: 0px 0px 10px;"&gt;&lt;SPAN class="" style="background: 0px 0px; border: 0px; font-size: 15px;"&gt;&lt;/SPAN&gt;&lt;/H1&gt;&lt;P&gt;&lt;SPAN style="background-color: #ffffff; border: 0px; background: 0px 0px; font-size: 15px; font-family: arial, helvetica, sans-serif;"&gt;Zing! Btw, it looks like there is an additional relationships resource that would expose the attribute rule properties within&amp;nbsp;a feature service in the ArcGIS REST API, introduced at version 10.7. So, maybe they are planning to implement what you are talking about soon.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #ffffff; border: 0px; background: 0px 0px; font-size: 15px; font-family: arial, helvetica, sans-serif;"&gt;&lt;A href="https://developers.arcgis.com/rest/services-reference/relationships-feature-service-.htm"&gt;https://developers.arcgis.com/rest/services-reference/relationships-feature-service-.htm&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Apr 2019 19:48:38 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-ideas/apply-relationship-class-rules-to-collector/idc-p/941542#M1061</guid>
      <dc:creator>MicahBabinski</dc:creator>
      <dc:date>2019-04-26T19:48:38Z</dc:date>
    </item>
  </channel>
</rss>

