<?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 Sequence, Rules, and Versioned Feature Service Not Working as Expected in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/sequence-rules-and-versioned-feature-service-not/m-p/119797#M4991</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Experiencing odd behavior when implementing a database sequence within a attribute rule on a versioned feature service.&amp;nbsp; This is only occurring with line feature services - points and polygon&amp;nbsp; &lt;SPAN&gt;sequences&amp;nbsp;&lt;/SPAN&gt;in the same environment work as expected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To start, I've been developing the rule on a local file geodatabase.&amp;nbsp; The calculation rule with the sequence is working as expected on my line feature class.&amp;nbsp; Increase by 1 on each insert or split.&amp;nbsp; Screen shot is attached - localSeq.png - 90008 - 90011 are new line features while 90012 - 90014 are splits.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I push the rule up to my feature service is where it goes odd.&amp;nbsp; I will create a new line feature and the sequence will say start with 1.&amp;nbsp; The next line feature I create will be 3, and the next line feature will be 5 - it is jumping by 2.&amp;nbsp; Now If I make a split off a line feature with the sequence of 5 - the new split feature will be sequence 6, next split will be 7 - splits jump up by 1.&amp;nbsp; Screenshot named&amp;nbsp;featureSeq.png attached, 90010 - 90018 are new line features and 90019-90021 are splits.&amp;nbsp; So adding new features jumps by 2 while splits jump by 1.&amp;nbsp; I expect all should jump by 1.&lt;BR /&gt;&lt;BR /&gt;Not sure if this a bug or intended but I'm at wits end attempting to work around this.&amp;nbsp; Little help would be appreciated.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 21 Oct 2019 16:15:00 GMT</pubDate>
    <dc:creator>AndrewAdamson</dc:creator>
    <dc:date>2019-10-21T16:15:00Z</dc:date>
    <item>
      <title>Sequence, Rules, and Versioned Feature Service Not Working as Expected</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/sequence-rules-and-versioned-feature-service-not/m-p/119797#M4991</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Experiencing odd behavior when implementing a database sequence within a attribute rule on a versioned feature service.&amp;nbsp; This is only occurring with line feature services - points and polygon&amp;nbsp; &lt;SPAN&gt;sequences&amp;nbsp;&lt;/SPAN&gt;in the same environment work as expected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To start, I've been developing the rule on a local file geodatabase.&amp;nbsp; The calculation rule with the sequence is working as expected on my line feature class.&amp;nbsp; Increase by 1 on each insert or split.&amp;nbsp; Screen shot is attached - localSeq.png - 90008 - 90011 are new line features while 90012 - 90014 are splits.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I push the rule up to my feature service is where it goes odd.&amp;nbsp; I will create a new line feature and the sequence will say start with 1.&amp;nbsp; The next line feature I create will be 3, and the next line feature will be 5 - it is jumping by 2.&amp;nbsp; Now If I make a split off a line feature with the sequence of 5 - the new split feature will be sequence 6, next split will be 7 - splits jump up by 1.&amp;nbsp; Screenshot named&amp;nbsp;featureSeq.png attached, 90010 - 90018 are new line features and 90019-90021 are splits.&amp;nbsp; So adding new features jumps by 2 while splits jump by 1.&amp;nbsp; I expect all should jump by 1.&lt;BR /&gt;&lt;BR /&gt;Not sure if this a bug or intended but I'm at wits end attempting to work around this.&amp;nbsp; Little help would be appreciated.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Oct 2019 16:15:00 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/sequence-rules-and-versioned-feature-service-not/m-p/119797#M4991</guid>
      <dc:creator>AndrewAdamson</dc:creator>
      <dc:date>2019-10-21T16:15:00Z</dc:date>
    </item>
  </channel>
</rss>

