<?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 What is the best practice for attribute rules that trigger other attribute rules in Attribute Rules Questions</title>
    <link>https://community.esri.com/t5/attribute-rules-questions/what-is-the-best-practice-for-attribute-rules-that/m-p/1148988#M333</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I was wondering what the best practice is for a calculation attribute rule that could potentially be triggered from another attribute rule.&lt;/P&gt;&lt;P&gt;An example case is, lets assume I am working with the Utility Network and I have a calculation rule on Insert for my StructureLine (e.g. Duct Bank), which automatically creates X StructureEdgeObject (e.g. Ducts) contained within it where X is a value provided through one of the Structure Edge attributes. At the same time I want to create Y StructureEdgeObject&amp;nbsp; (e.g. SubDucts) contained within each Duct essentially creating a hierarchy of:&lt;/P&gt;&lt;P&gt;Duct Bank -&amp;gt; Duct -&amp;gt; Sub Duct&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Would it be better to have an attribute calculation rule on my StructureEdgeObject class which creates Y Sub Ducts every time a Duct is created (either from the StructureLine attribute rule or even when the user creates a duct manually and not through an attribute rule) ? Or is it better to create the Ducts and the Sub Ducts within the attribute calculation rule of the StructureLine class?&lt;/P&gt;&lt;P&gt;Are there any disadvantages doing it one way or the other?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 01 Mar 2022 06:58:41 GMT</pubDate>
    <dc:creator>omar-marji</dc:creator>
    <dc:date>2022-03-01T06:58:41Z</dc:date>
    <item>
      <title>What is the best practice for attribute rules that trigger other attribute rules</title>
      <link>https://community.esri.com/t5/attribute-rules-questions/what-is-the-best-practice-for-attribute-rules-that/m-p/1148988#M333</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I was wondering what the best practice is for a calculation attribute rule that could potentially be triggered from another attribute rule.&lt;/P&gt;&lt;P&gt;An example case is, lets assume I am working with the Utility Network and I have a calculation rule on Insert for my StructureLine (e.g. Duct Bank), which automatically creates X StructureEdgeObject (e.g. Ducts) contained within it where X is a value provided through one of the Structure Edge attributes. At the same time I want to create Y StructureEdgeObject&amp;nbsp; (e.g. SubDucts) contained within each Duct essentially creating a hierarchy of:&lt;/P&gt;&lt;P&gt;Duct Bank -&amp;gt; Duct -&amp;gt; Sub Duct&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Would it be better to have an attribute calculation rule on my StructureEdgeObject class which creates Y Sub Ducts every time a Duct is created (either from the StructureLine attribute rule or even when the user creates a duct manually and not through an attribute rule) ? Or is it better to create the Ducts and the Sub Ducts within the attribute calculation rule of the StructureLine class?&lt;/P&gt;&lt;P&gt;Are there any disadvantages doing it one way or the other?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 01 Mar 2022 06:58:41 GMT</pubDate>
      <guid>https://community.esri.com/t5/attribute-rules-questions/what-is-the-best-practice-for-attribute-rules-that/m-p/1148988#M333</guid>
      <dc:creator>omar-marji</dc:creator>
      <dc:date>2022-03-01T06:58:41Z</dc:date>
    </item>
  </channel>
</rss>

