<?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 Legacy Data - How to handle in UN in ArcGIS Utility Network Questions</title>
    <link>https://community.esri.com/t5/arcgis-utility-network-questions/legacy-data-how-to-handle-in-un/m-p/1032051#M989</link>
    <description>&lt;P&gt;Hi everyone-&lt;/P&gt;&lt;P&gt;We are migrating a pretty large gas data set to the UN. We have a situation where we have certain legacy data that is a part of the existing GIS, but we don't want it to necessarily have the same rules as newer data?&lt;/P&gt;&lt;P&gt;For a quick example, an existing plastic to plastic connection is valid, but we don't want users to be able to add a new one.&lt;/P&gt;&lt;P&gt;Does anyone have ideas on how we could implement this?&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Lifecycle status?&lt;/LI&gt;&lt;LI&gt;Minimal connectivity rules with very explicit attribute rules?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Any thoughts or pervious experience would be very helpful!!&lt;/P&gt;</description>
    <pubDate>Tue, 02 Mar 2021 18:41:45 GMT</pubDate>
    <dc:creator>TJ_Houle</dc:creator>
    <dc:date>2021-03-02T18:41:45Z</dc:date>
    <item>
      <title>Legacy Data - How to handle in UN</title>
      <link>https://community.esri.com/t5/arcgis-utility-network-questions/legacy-data-how-to-handle-in-un/m-p/1032051#M989</link>
      <description>&lt;P&gt;Hi everyone-&lt;/P&gt;&lt;P&gt;We are migrating a pretty large gas data set to the UN. We have a situation where we have certain legacy data that is a part of the existing GIS, but we don't want it to necessarily have the same rules as newer data?&lt;/P&gt;&lt;P&gt;For a quick example, an existing plastic to plastic connection is valid, but we don't want users to be able to add a new one.&lt;/P&gt;&lt;P&gt;Does anyone have ideas on how we could implement this?&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Lifecycle status?&lt;/LI&gt;&lt;LI&gt;Minimal connectivity rules with very explicit attribute rules?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Any thoughts or pervious experience would be very helpful!!&lt;/P&gt;</description>
      <pubDate>Tue, 02 Mar 2021 18:41:45 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-utility-network-questions/legacy-data-how-to-handle-in-un/m-p/1032051#M989</guid>
      <dc:creator>TJ_Houle</dc:creator>
      <dc:date>2021-03-02T18:41:45Z</dc:date>
    </item>
    <item>
      <title>Re: Legacy Data - How to handle in UN</title>
      <link>https://community.esri.com/t5/arcgis-utility-network-questions/legacy-data-how-to-handle-in-un/m-p/1032069#M990</link>
      <description>Best option is an attribute rule to restrict the edit. This rule would be disabled when the data is loaded and then enabled once editing has started.&lt;BR /&gt;I do not have a rules that meets your needs prebuild, but an example of a constraint here can be found here:&lt;BR /&gt;&lt;A href="https://github.com/Esri/arcade-expressions/blob/master/attribute_rule_constraint/only_at_start_end.md" target="_blank"&gt;https://github.com/Esri/arcade-expressions/blob/master/attribute_rule_constraint/only_at_start_end.md&lt;/A&gt;</description>
      <pubDate>Tue, 02 Mar 2021 18:56:59 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-utility-network-questions/legacy-data-how-to-handle-in-un/m-p/1032069#M990</guid>
      <dc:creator>MikeMillerGIS</dc:creator>
      <dc:date>2021-03-02T18:56:59Z</dc:date>
    </item>
  </channel>
</rss>

