<?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 Re: Sync-Enabled Feature Service With Archiving Seems to Download Full Dataset on Sync in ArcGIS Enterprise Questions</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-questions/sync-enabled-feature-service-with-archiving-seems/m-p/1534357#M40500</link>
    <description>&lt;P&gt;I've learned a *little* more about this behavior, but still don't understand it.&amp;nbsp; We've found that when we follow similar steps in ArcPro (download the mobile geodatabase, make updates in Pro to the service, then sync to the mobile geodatabase) that the gdb_from_date was only updated for features that actually changed.&amp;nbsp; Which is different than the behavior we see when a sync is performed using the runtime API.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So, I guess this is a little more data, but not more knowledge.&lt;/P&gt;</description>
    <pubDate>Tue, 03 Sep 2024 13:56:24 GMT</pubDate>
    <dc:creator>EdwardBlair</dc:creator>
    <dc:date>2024-09-03T13:56:24Z</dc:date>
    <item>
      <title>Sync-Enabled Feature Service With Archiving Seems to Download Full Dataset on Sync</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/sync-enabled-feature-service-with-archiving-seems/m-p/1526853#M40406</link>
      <description>&lt;P&gt;We're experimenting with use of sync-enabled feature services to support a mobile application.&amp;nbsp; We're using archiving as opposed to versioning to detect changes.&amp;nbsp; In a simple test I added a new feature to the parent feature class in the enterprise geodatabase to see if it would sync down to the client (a runtime geodatabase on a laptop).&amp;nbsp; Eventually the new feature showed up on the client -- which is good.&amp;nbsp; &amp;nbsp;However, I noticed that ALL of the features in the runtime gdb had the same gdb_from_date value as my new feature.&amp;nbsp; I would have expected my new feature to have a layer gdb_from_date than all other records.&amp;nbsp; &amp;nbsp;Which prompts my question, what/how much information is actually transferred to the client on a "sync"?&amp;nbsp; &amp;nbsp;I thought it would be only the changes since the last "create replica" or "sync replica" operation.&amp;nbsp; &amp;nbsp;But it seems like it might be re-sending the entire dataset.&lt;/P&gt;&lt;P&gt;Any insights would be much appreciated.&lt;/P&gt;</description>
      <pubDate>Sun, 25 Aug 2024 14:16:06 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/sync-enabled-feature-service-with-archiving-seems/m-p/1526853#M40406</guid>
      <dc:creator>EdwardBlair</dc:creator>
      <dc:date>2024-08-25T14:16:06Z</dc:date>
    </item>
    <item>
      <title>Re: Sync-Enabled Feature Service With Archiving Seems to Download Full Dataset on Sync</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/sync-enabled-feature-service-with-archiving-seems/m-p/1534357#M40500</link>
      <description>&lt;P&gt;I've learned a *little* more about this behavior, but still don't understand it.&amp;nbsp; We've found that when we follow similar steps in ArcPro (download the mobile geodatabase, make updates in Pro to the service, then sync to the mobile geodatabase) that the gdb_from_date was only updated for features that actually changed.&amp;nbsp; Which is different than the behavior we see when a sync is performed using the runtime API.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So, I guess this is a little more data, but not more knowledge.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Sep 2024 13:56:24 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/sync-enabled-feature-service-with-archiving-seems/m-p/1534357#M40500</guid>
      <dc:creator>EdwardBlair</dc:creator>
      <dc:date>2024-09-03T13:56:24Z</dc:date>
    </item>
  </channel>
</rss>

