<?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 a replica-compatible version of Attribute Rules in ArcGIS Enterprise Ideas</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-ideas/create-a-replica-compatible-version-of-attribute/idi-p/1333748</link>
    <description>&lt;P&gt;Per Esri's documentation, &lt;A href="https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/replication-with-advanced-geodatabase-datasets.htm" target="_blank" rel="noopener"&gt;Attribute Rules and Contingent Values are not supported in geodatabase replicas&lt;/A&gt;. I reached out to Esri Technical Support to ask what would happen if we implemented Attribute Rules on a child geodatabase participating in a two-way replica (Esri case 03438244). They tested that workflow and did not turn up any issues, but reiterated that it is not a supported workflow and recommended against implementing it without taking regular backups for disaster recovery purposes.&lt;/P&gt;&lt;P&gt;I would like to see Esri create a supported workflow for using Attribute Rules on replica databases. While I do not need to replicate the rules between the parent and the child, I can imagine that it would be useful functionality. Here is our current workflow:&lt;/P&gt;&lt;P&gt;- County GIS has the master NG911 geodatabase. This includes, but is not limited to, address points and road centerlines.&lt;/P&gt;&lt;P&gt;- City GIS (my organization) has a child two-way replica database of the master NG911 geodatabase. We are responsible for maintaining geodata within our city limits, as we are the authoritative source for addressing in this area.&lt;/P&gt;&lt;P&gt;- Each address point and road centerline has attributes related to the zones that intersect. For example, an address point must be assigned a fire response zone and a law response zone. The city uses Attribute Rules to auto-populate these fields based on their intersection with the polygon layers that track that information.&lt;/P&gt;&lt;P&gt;We have several other rules (auto-incrementing IDs, for example), but one example of the utility of Attribute Rules should be sufficient.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 29 Sep 2023 14:20:45 GMT</pubDate>
    <dc:creator>AmyRoust</dc:creator>
    <dc:date>2023-09-29T14:20:45Z</dc:date>
    <item>
      <title>Create a replica-compatible version of Attribute Rules</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-ideas/create-a-replica-compatible-version-of-attribute/idi-p/1333748</link>
      <description>&lt;P&gt;Per Esri's documentation, &lt;A href="https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/replication-with-advanced-geodatabase-datasets.htm" target="_blank" rel="noopener"&gt;Attribute Rules and Contingent Values are not supported in geodatabase replicas&lt;/A&gt;. I reached out to Esri Technical Support to ask what would happen if we implemented Attribute Rules on a child geodatabase participating in a two-way replica (Esri case 03438244). They tested that workflow and did not turn up any issues, but reiterated that it is not a supported workflow and recommended against implementing it without taking regular backups for disaster recovery purposes.&lt;/P&gt;&lt;P&gt;I would like to see Esri create a supported workflow for using Attribute Rules on replica databases. While I do not need to replicate the rules between the parent and the child, I can imagine that it would be useful functionality. Here is our current workflow:&lt;/P&gt;&lt;P&gt;- County GIS has the master NG911 geodatabase. This includes, but is not limited to, address points and road centerlines.&lt;/P&gt;&lt;P&gt;- City GIS (my organization) has a child two-way replica database of the master NG911 geodatabase. We are responsible for maintaining geodata within our city limits, as we are the authoritative source for addressing in this area.&lt;/P&gt;&lt;P&gt;- Each address point and road centerline has attributes related to the zones that intersect. For example, an address point must be assigned a fire response zone and a law response zone. The city uses Attribute Rules to auto-populate these fields based on their intersection with the polygon layers that track that information.&lt;/P&gt;&lt;P&gt;We have several other rules (auto-incrementing IDs, for example), but one example of the utility of Attribute Rules should be sufficient.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 29 Sep 2023 14:20:45 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-ideas/create-a-replica-compatible-version-of-attribute/idi-p/1333748</guid>
      <dc:creator>AmyRoust</dc:creator>
      <dc:date>2023-09-29T14:20:45Z</dc:date>
    </item>
  </channel>
</rss>

