{"id":2967139,"date":"2026-05-26T07:00:18","date_gmt":"2026-05-26T14:00:18","guid":{"rendered":"https:\/\/www.esri.com\/arcgis-blog\/?post_type=blog&#038;p=2967139"},"modified":"2026-05-28T06:37:04","modified_gmt":"2026-05-28T13:37:04","slug":"knowledge-graph-sync-delta-download-behaviors","status":"publish","type":"blog","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-knowledge\/developers\/knowledge-graph-sync-delta-download-behaviors","title":{"rendered":"Knowledge graph sync behaviors for attribute filtered replicas"},"author":408840,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"_acf_changed":false,"_searchwp_excluded":""},"categories":[738191],"tags":[40691,42301,768752,98592],"industry":[],"product":[36571,762232,36861],"class_list":["post-2967139","blog","type-blog","status-publish","format-standard","hentry","category-developers","tag-analytics","tag-arcgis-enterprise","tag-knowledge-graph","tag-sync","product-arcgis-enterprise","product-arcgis-knowledge","product-api-rest"],"acf":{"authors":[{"ID":408840,"user_firstname":"Jim","user_lastname":"Spoden","nickname":"Jim Spoden","user_nicename":"jspodenesri-com_esriinc","display_name":"Jim Spoden","user_email":"jspoden@esri.com","user_url":"","user_registered":"2025-10-01 20:42:32","user_description":"Jim is a Product Engineer on the ArcGIS Knowledge team at Esri. He brings varied experience from environmental remote sensing and science communication to global trade compliance. Outside the office he enjoys cooking, reading, and making stained glass but is often found wrangling his misbehaving cats.","user_avatar":"<img data-del=\"avatar\" src='https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/05\/20240424_162305.jpg' class='avatar pp-user-avatar avatar-96 photo ' height='96' width='96'\/>"}],"short_description":"Synchronize delta download behaviors for attribute filtered knowledge graph replicas","flexible_content":[{"acf_fc_layout":"content","content":"<p>This blog article describes scenarios in which the synchronize delta download behavior for attribute filtered replicas may appear in unexpected ways. Attribute filters in knowledge graph replicas are in preview at 12.1 due to these behaviors.<\/p>\n<h4>Problem<\/h4>\n<p>When synchronizing an ArcGIS Knowledge replica using\u00a0delta download, some edits may appear to be missing or returned in an unexpected form. For example, entities may not be returned as adds or deletes when they appear to move into or out of the replica definition, and related content such as relationships, provenance, or documents may not be included.<\/p>\n<h4>Cause<\/h4>\n<p>This behavior occurs because ArcGIS Knowledge synchronize delta download uses a\u00a0change tracking model, not an archiving model. The service tracks what has changed since the last synchronization, but it does not store historical attribute membership or previous replica participation for entities, relationships, or related objects. As a result, the service cannot always infer whether an instance previously belonged to a replica when attribute filters are used.<\/p>\n<h4>Workaround<\/h4>\n<p>If a complete and current representation of the replica data is required, particularly after encountering any of the edge cases described below, create or refresh the replica using a\u00a0snapshot. A snapshot download materializes the full replica contents and avoids ambiguity introduced by change tracking semantics.<\/p>\n<p>The following guide can help you choose between snapshot or delta download when synchronizing an ArcGIS Knowledge replica.<\/p>\n<p>Use\u00a0delta download\u00a0in the following scenarios:<\/p>\n<ul>\n<li>You expect incremental changes and are comfortable with change tracking semantics.<\/li>\n<li>Attribute\u2011filtered replicas are stable, and entities are not frequently moving into or out of the replica definition.<\/li>\n<li>Missing adds or deletes due to update\u2011in or update\u2011out scenarios are acceptable.<\/li>\n<\/ul>\n<p>Use a\u00a0snapshot\u00a0in the following scenarios:<\/p>\n<ul>\n<li>You need a\u00a0complete and authoritative representation\u00a0of the replica data.<\/li>\n<li>Entities, relationships, provenance, or documents may have moved into or out of the replica definition since the last synchronization.<\/li>\n<li>You encounter any of the edge cases described in this article and require the replica to be fully reconciled.<\/li>\n<\/ul>\n<p>Snapshot downloads materialize the full replica contents and avoid ambiguity introduced by change tracking, attribute filters, and historical membership limitations.<\/p>\n<h3><strong>Entity behavior<\/strong><\/h3>\n<table>\n<tbody>\n<tr>\n<td width=\"208\"><strong>Scenario<\/strong><\/td>\n<td width=\"208\"><strong>Result<\/strong><\/td>\n<td width=\"208\"><strong>Delta output<\/strong><\/td>\n<\/tr>\n<tr>\n<td width=\"208\">Add entity inside the replica definition<\/td>\n<td width=\"208\">The entity is returned as an add.<\/td>\n<td width=\"208\">\n<pre>add: { entity }<\/pre>\n<\/td>\n<\/tr>\n<tr>\n<td width=\"208\">Update entity inside the replica definition<\/td>\n<td width=\"208\">The entity is returned as an update.<\/td>\n<td width=\"208\">\n<pre>upd: { entity }<\/pre>\n<\/td>\n<\/tr>\n<tr>\n<td width=\"208\">Update entity moving into the replica definition<\/td>\n<td width=\"208\">The entity is returned as an update, not an add. See explanation.<\/td>\n<td width=\"208\">\n<pre>upd: { entity }<\/pre>\n<\/td>\n<\/tr>\n<tr>\n<td width=\"208\">Update entity moving out of the replica definition<\/td>\n<td width=\"208\">No delete is returned. See explanation<\/td>\n<td width=\"208\">\u2014<\/td>\n<\/tr>\n<tr>\n<td width=\"208\">Delete entity inside the replica definition<\/td>\n<td width=\"208\">The entity is returned as a delete.<\/td>\n<td width=\"208\">\n<pre>del: { entity }<\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>\u00a0<\/strong>The following explanations provide further context related to entity behaviors.<\/p>\n<ul>\n<li>When updating an entity moving into the replica, the entity is returned as an update, not an add. Since the system does not track historical replica membership, it cannot determine whether the entity previously belonged to the replica. This behavior matches ArcGIS Online synchronize semantics.<\/li>\n<li>When updating an entity moving out of a replica, no delete is returned. This is because the service cannot infer that the entity should be deleted from the replica because historical attribution is not stored.<\/li>\n<\/ul>\n<h3><strong>Relationship behavior<\/strong><\/h3>\n<p>Relationships participate in a replica only when both endpoints participate in the replica definition.<\/p>\n<table width=\"623\">\n<tbody>\n<tr>\n<td width=\"208\"><strong>Scenario<\/strong><\/td>\n<td width=\"208\"><strong>Result<\/strong><\/td>\n<td width=\"208\"><strong>Delta output<\/strong><\/td>\n<\/tr>\n<tr>\n<td width=\"208\">Add relationship where both endpoints are in the replica<\/td>\n<td width=\"208\">Relationship is returned as an add.<\/td>\n<td width=\"208\">\n<pre>add: { relationship }<\/pre>\n<\/td>\n<\/tr>\n<tr>\n<td width=\"208\">Add relationship where only one endpoint is in the replica<\/td>\n<td width=\"208\">The relationship is not returned. See explanation.<\/td>\n<td width=\"208\">\u2014<\/td>\n<\/tr>\n<tr>\n<td width=\"208\">Update entity out of the replica definition (with relationships)<\/td>\n<td width=\"208\">Neither the entity nor its relationships are returned. See explanation.<\/td>\n<td width=\"208\">\u2014<\/td>\n<\/tr>\n<tr>\n<td width=\"208\">Update entity into the replica definition (with relationships)<\/td>\n<td width=\"208\">The entity is returned as an update. See explanation.<\/td>\n<td width=\"208\">\n<pre>upd: { entity }<\/pre>\n<\/td>\n<\/tr>\n<tr>\n<td width=\"208\">Delete relationship<\/td>\n<td width=\"208\">The relationship is returned as a delete.<\/td>\n<td width=\"208\">\n<pre>del: { relationship }<\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>\u00a0<\/strong>The following explanations provide further context related to relationship behaviors.<\/p>\n<ul>\n<li>Adding a relationship where only one endpoint is in the replica will result in the relationship not being returned in the delta download. As a result, the relationship does not exist in the replica because both endpoints are not included.<\/li>\n<li>Updating an entity out of a replica, the entity update is not reported due to change tracking semantics. Additionally, relationships are not returned because an endpoint no longer participates in the replica.<\/li>\n<li>The relationship connections are not included when an entity update moves into the replica.<\/li>\n<\/ul>\n<h3><strong>Provenance behavior<\/strong><\/h3>\n<table>\n<tbody>\n<tr>\n<td width=\"208\">Scenario<\/td>\n<td width=\"208\">Result<\/td>\n<td width=\"208\">Behavior<\/td>\n<\/tr>\n<tr>\n<td width=\"208\">Add, update, or delete provenance<\/td>\n<td width=\"208\">Provenance add, update, or delete is returned.<\/td>\n<td style=\"text-align: left\" width=\"208\">\n<pre>Add:\u00a0add: { provenance }\r\n\r\nUpdate:\u00a0upd: { provenance }\r\n\r\nDelete:\u00a0del: { provenance }<\/pre>\n<p>&nbsp;<\/td>\n<\/tr>\n<tr>\n<td width=\"208\">Entity or relationship moves into the replica with provenance deleted<\/td>\n<td width=\"208\">Entity or relationship update is returned. Provenance delete is returned. See explanation.<\/td>\n<td style=\"text-align: left\" width=\"208\">\n<pre>upd: { entity | relationship }\r\n\r\ndel: { provenance }<\/pre>\n<p>&nbsp;<\/td>\n<\/tr>\n<tr>\n<td width=\"208\">Entity or relationship moves out of the replica with provenance deleted<\/td>\n<td width=\"208\">No results are returned. See explanation.<\/td>\n<td width=\"208\">\u2014<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The following explanations provide further context related to provenance behaviors.<\/p>\n<ul>\n<li>A provenance delete may be returned when an entity or relationship moves into the replica, even if the replica never previously included that provenance, due to change tracking semantics.<\/li>\n<\/ul>\n<ul>\n<li>No results are returned when an entity or relationship moves out of the replica because the replica is unaware that the data no longer participates in the replica definition.<\/li>\n<\/ul>\n<h3><strong>Source document behavior<\/strong><\/h3>\n<table>\n<tbody>\n<tr>\n<td width=\"208\"><strong>Scenario<\/strong><\/td>\n<td width=\"208\"><strong>Result<\/strong><\/td>\n<td width=\"208\"><strong>Delta Output<\/strong><\/td>\n<\/tr>\n<tr>\n<td width=\"208\">Add entity or relationship with provenance and source document<\/td>\n<td width=\"208\">All related objects are returned.<\/td>\n<td width=\"208\">\n<pre>add: { entity | relationship, provenance, source document }<\/pre>\n<\/td>\n<\/tr>\n<tr>\n<td width=\"208\">Update entity or relationship<\/td>\n<td width=\"208\">Only the entity or relationship is returned. See explanation.<\/td>\n<td width=\"208\">\n<pre>upd: { entity | relationship }<\/pre>\n<\/td>\n<\/tr>\n<tr>\n<td width=\"208\">Update provenance<\/td>\n<td width=\"208\">Provenance update is returned. Source documents are returned as adds. See explanation.<\/p>\n<p><strong>\u00a0<\/strong><\/td>\n<td width=\"208\">\n<pre>upd: { provenance }\r\n\r\nadd: { source document }<\/pre>\n<\/td>\n<\/tr>\n<tr>\n<td width=\"208\">Delete source document<\/td>\n<td width=\"208\">Source document delete is returned. See explanation.<\/td>\n<td width=\"208\">\n<pre>del: { source document }<\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>\u00a0<\/strong>The following explanations provide further context related to source document behaviors.<\/p>\n<ul>\n<li>When updating an entity or relationship, the provenance and source documents are not included because attribute history is not stored.<\/li>\n<li>Source documents are included when updating provenance to ensure the replica has complete information when provenance source types are updated.<\/li>\n<li>Deleting a source document does not validate or update provenance references. A provenance may reference a source document that no longer exists.<\/li>\n<\/ul>\n<h3><strong>Connected documents (HasDocument relationships) behavior<\/strong><\/h3>\n<table>\n<tbody>\n<tr>\n<td width=\"208\"><strong>Scenario<\/strong><\/td>\n<td width=\"208\"><strong>Result<\/strong><\/td>\n<td width=\"208\"><strong>Delta Output<\/strong><\/td>\n<\/tr>\n<tr>\n<td width=\"208\">Add HasDocument relationship<\/td>\n<td width=\"208\">The relationship and destination document are returned. See explanation.<\/p>\n<p>&nbsp;<\/td>\n<td width=\"208\">\n<pre>add: { hasDocument, document }<\/pre>\n<\/td>\n<\/tr>\n<tr>\n<td width=\"208\">Update entity into the replica definition<\/td>\n<td width=\"208\">The entity is returned as an update. See explanation.<\/td>\n<td width=\"208\">\n<pre>upd: { entity }<\/pre>\n<\/td>\n<\/tr>\n<tr>\n<td width=\"208\">Delete HasDocument relationship<\/td>\n<td width=\"208\">Only the relationship delete is returned. See explanation.<\/td>\n<td width=\"208\">\n<pre>del: { hasDocument }<\/pre>\n<\/td>\n<\/tr>\n<tr>\n<td width=\"208\">Delete HasDocument and delete document<\/td>\n<td width=\"208\">Both the relationship and document deletes are returned.<\/td>\n<td width=\"208\">\n<pre>del: { hasDocument, document }<\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The following explanations provide further context related to connected document behaviors.<\/p>\n<ul>\n<li>When adding a HasDocument relationship, the system cannot efficiently determine whether the document already exists elsewhere in the replica. As a result, duplicates may be returned. Clients should upsert documents into their replica.<\/li>\n<li>When updating an entity into the replica, the connected HasDocument relationships and documents are not included.<\/li>\n<li>Deleting a HasDocument relationship will not delete the destination document if it still exists in the service.<\/li>\n<\/ul>\n<h3><strong>Additional Information<\/strong><\/h3>\n<p>Similar synchronize semantics are used in ArcGIS Online. These behaviors are expected and occur due to the following factors:<\/p>\n<ul>\n<li>Change tracking\u2013based synchronization<\/li>\n<li>Attribute\u2011filtered replica definitions<\/li>\n<li>Performance constraints when evaluating historical relationships<\/li>\n<\/ul>\n"}],"related_articles":[{"ID":2966712,"post_author":"408840","post_date":"2026-05-26 07:00:55","post_date_gmt":"2026-05-26 14:00:55","post_content":"","post_title":"Best practices for knowledge graph service sync performance","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"closed","post_password":"","post_name":"best-practices-for-knowledge-graph-service-sync-performance","to_ping":"","pinged":"","post_modified":"2026-05-28 14:56:16","post_modified_gmt":"2026-05-28 21:56:16","post_content_filtered":"","post_parent":0,"guid":"https:\/\/www.esri.com\/arcgis-blog\/?post_type=blog&#038;p=2966712","menu_order":0,"post_type":"blog","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2963672,"post_author":"9602","post_date":"2026-05-21 15:50:40","post_date_gmt":"2026-05-21 22:50:40","post_content":"","post_title":"What's new in ArcGIS Knowledge 12.1 (2026 Q2)","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"closed","post_password":"","post_name":"whats-new-in-arcgis-knowledge-12-1","to_ping":"","pinged":"","post_modified":"2026-05-29 12:57:51","post_modified_gmt":"2026-05-29 19:57:51","post_content_filtered":"","post_parent":0,"guid":"https:\/\/www.esri.com\/arcgis-blog\/?post_type=blog&#038;p=2963672","menu_order":0,"post_type":"blog","post_mime_type":"","comment_count":"0","filter":"raw"}],"show_article_image":true,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/05\/knowledge-sync-filter-behavior-AdobeStock-240245083.png","wide_image":false},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v25.9 (Yoast SEO v25.9) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Knowledge graph synchronize delta download behavior<\/title>\n<meta name=\"description\" content=\"Understand ArcGIS Knowledge graph sync delta download behavior with attribute filters, including when to use a replica snapshot.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-knowledge\/developers\/knowledge-graph-sync-delta-download-behaviors\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Knowledge graph sync behaviors for attribute filtered replicas\" \/>\n<meta property=\"og:description\" content=\"Understand ArcGIS Knowledge graph sync delta download behavior with attribute filters, including when to use a replica snapshot.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-knowledge\/developers\/knowledge-graph-sync-delta-download-behaviors\" \/>\n<meta property=\"og:site_name\" content=\"ArcGIS Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/esrigis\/\" \/>\n<meta property=\"article:modified_time\" content=\"2026-05-28T13:37:04+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:site\" content=\"@ESRI\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":[\"Article\",\"BlogPosting\"],\"@id\":\"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-knowledge\/developers\/knowledge-graph-sync-delta-download-behaviors#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-knowledge\/developers\/knowledge-graph-sync-delta-download-behaviors\"},\"author\":{\"name\":\"Jim Spoden\",\"@id\":\"https:\/\/www.esri.com\/arcgis-blog\/#\/schema\/person\/4db06c9172c0000305b7c48f8bae853f\"},\"headline\":\"Knowledge graph sync behaviors for attribute filtered replicas\",\"datePublished\":\"2026-05-26T14:00:18+00:00\",\"dateModified\":\"2026-05-28T13:37:04+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-knowledge\/developers\/knowledge-graph-sync-delta-download-behaviors\"},\"wordCount\":8,\"publisher\":{\"@id\":\"https:\/\/www.esri.com\/arcgis-blog\/#organization\"},\"keywords\":[\"analytics\",\"ArcGIS Enterprise\",\"knowledge graph\",\"sync\"],\"articleSection\":[\"Developers\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-knowledge\/developers\/knowledge-graph-sync-delta-download-behaviors\",\"url\":\"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-knowledge\/developers\/knowledge-graph-sync-delta-download-behaviors\",\"name\":\"Knowledge graph synchronize delta download behavior\",\"isPartOf\":{\"@id\":\"https:\/\/www.esri.com\/arcgis-blog\/#website\"},\"datePublished\":\"2026-05-26T14:00:18+00:00\",\"dateModified\":\"2026-05-28T13:37:04+00:00\",\"description\":\"Understand ArcGIS Knowledge graph sync delta download behavior with attribute filters, including when to use a replica snapshot.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-knowledge\/developers\/knowledge-graph-sync-delta-download-behaviors#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-knowledge\/developers\/knowledge-graph-sync-delta-download-behaviors\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-knowledge\/developers\/knowledge-graph-sync-delta-download-behaviors#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.esri.com\/arcgis-blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Knowledge graph sync behaviors for attribute filtered replicas\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.esri.com\/arcgis-blog\/#website\",\"url\":\"https:\/\/www.esri.com\/arcgis-blog\/\",\"name\":\"ArcGIS Blog\",\"description\":\"Get insider info from Esri product teams\",\"publisher\":{\"@id\":\"https:\/\/www.esri.com\/arcgis-blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.esri.com\/arcgis-blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.esri.com\/arcgis-blog\/#organization\",\"name\":\"Esri\",\"url\":\"https:\/\/www.esri.com\/arcgis-blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.esri.com\/arcgis-blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2018\/04\/Esri.png\",\"contentUrl\":\"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2018\/04\/Esri.png\",\"width\":400,\"height\":400,\"caption\":\"Esri\"},\"image\":{\"@id\":\"https:\/\/www.esri.com\/arcgis-blog\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/esrigis\/\",\"https:\/\/x.com\/ESRI\",\"https:\/\/www.linkedin.com\/company\/5311\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.esri.com\/arcgis-blog\/#\/schema\/person\/4db06c9172c0000305b7c48f8bae853f\",\"name\":\"Jim Spoden\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.esri.com\/arcgis-blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/05\/20240424_162305.jpg\",\"contentUrl\":\"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/05\/20240424_162305.jpg\",\"caption\":\"Jim Spoden\"},\"description\":\"Jim is a Product Engineer on the ArcGIS Knowledge team at Esri. He brings varied experience from environmental remote sensing and science communication to global trade compliance. Outside the office he enjoys cooking, reading, and making stained glass but is often found wrangling his misbehaving cats.\",\"url\":\"https:\/\/www.esri.com\/arcgis-blog\/author\/jspodenesri-com_esriinc\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Knowledge graph synchronize delta download behavior","description":"Understand ArcGIS Knowledge graph sync delta download behavior with attribute filters, including when to use a replica snapshot.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-knowledge\/developers\/knowledge-graph-sync-delta-download-behaviors","og_locale":"en_US","og_type":"article","og_title":"Knowledge graph sync behaviors for attribute filtered replicas","og_description":"Understand ArcGIS Knowledge graph sync delta download behavior with attribute filters, including when to use a replica snapshot.","og_url":"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-knowledge\/developers\/knowledge-graph-sync-delta-download-behaviors","og_site_name":"ArcGIS Blog","article_publisher":"https:\/\/www.facebook.com\/esrigis\/","article_modified_time":"2026-05-28T13:37:04+00:00","twitter_card":"summary_large_image","twitter_site":"@ESRI","twitter_misc":{"Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":["Article","BlogPosting"],"@id":"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-knowledge\/developers\/knowledge-graph-sync-delta-download-behaviors#article","isPartOf":{"@id":"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-knowledge\/developers\/knowledge-graph-sync-delta-download-behaviors"},"author":{"name":"Jim Spoden","@id":"https:\/\/www.esri.com\/arcgis-blog\/#\/schema\/person\/4db06c9172c0000305b7c48f8bae853f"},"headline":"Knowledge graph sync behaviors for attribute filtered replicas","datePublished":"2026-05-26T14:00:18+00:00","dateModified":"2026-05-28T13:37:04+00:00","mainEntityOfPage":{"@id":"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-knowledge\/developers\/knowledge-graph-sync-delta-download-behaviors"},"wordCount":8,"publisher":{"@id":"https:\/\/www.esri.com\/arcgis-blog\/#organization"},"keywords":["analytics","ArcGIS Enterprise","knowledge graph","sync"],"articleSection":["Developers"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-knowledge\/developers\/knowledge-graph-sync-delta-download-behaviors","url":"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-knowledge\/developers\/knowledge-graph-sync-delta-download-behaviors","name":"Knowledge graph synchronize delta download behavior","isPartOf":{"@id":"https:\/\/www.esri.com\/arcgis-blog\/#website"},"datePublished":"2026-05-26T14:00:18+00:00","dateModified":"2026-05-28T13:37:04+00:00","description":"Understand ArcGIS Knowledge graph sync delta download behavior with attribute filters, including when to use a replica snapshot.","breadcrumb":{"@id":"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-knowledge\/developers\/knowledge-graph-sync-delta-download-behaviors#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-knowledge\/developers\/knowledge-graph-sync-delta-download-behaviors"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-knowledge\/developers\/knowledge-graph-sync-delta-download-behaviors#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.esri.com\/arcgis-blog\/"},{"@type":"ListItem","position":2,"name":"Knowledge graph sync behaviors for attribute filtered replicas"}]},{"@type":"WebSite","@id":"https:\/\/www.esri.com\/arcgis-blog\/#website","url":"https:\/\/www.esri.com\/arcgis-blog\/","name":"ArcGIS Blog","description":"Get insider info from Esri product teams","publisher":{"@id":"https:\/\/www.esri.com\/arcgis-blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.esri.com\/arcgis-blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.esri.com\/arcgis-blog\/#organization","name":"Esri","url":"https:\/\/www.esri.com\/arcgis-blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.esri.com\/arcgis-blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2018\/04\/Esri.png","contentUrl":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2018\/04\/Esri.png","width":400,"height":400,"caption":"Esri"},"image":{"@id":"https:\/\/www.esri.com\/arcgis-blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/esrigis\/","https:\/\/x.com\/ESRI","https:\/\/www.linkedin.com\/company\/5311\/"]},{"@type":"Person","@id":"https:\/\/www.esri.com\/arcgis-blog\/#\/schema\/person\/4db06c9172c0000305b7c48f8bae853f","name":"Jim Spoden","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.esri.com\/arcgis-blog\/#\/schema\/person\/image\/","url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/05\/20240424_162305.jpg","contentUrl":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/05\/20240424_162305.jpg","caption":"Jim Spoden"},"description":"Jim is a Product Engineer on the ArcGIS Knowledge team at Esri. He brings varied experience from environmental remote sensing and science communication to global trade compliance. Outside the office he enjoys cooking, reading, and making stained glass but is often found wrangling his misbehaving cats.","url":"https:\/\/www.esri.com\/arcgis-blog\/author\/jspodenesri-com_esriinc"}]}},"text_date":"May 26, 2026","author_name":"Jim Spoden","author_page":"https:\/\/www.esri.com\/arcgis-blog\/author\/jspodenesri-com_esriinc","custom_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/08\/Newsroom-Keyart-Wide-1920-x-1080.jpg","primary_product":"ArcGIS Knowledge","tag_data":[{"term_id":40691,"name":"analytics","slug":"analytics","term_group":0,"term_taxonomy_id":40691,"taxonomy":"post_tag","description":"","parent":0,"count":56,"filter":"raw"},{"term_id":42301,"name":"ArcGIS Enterprise","slug":"arcgis-enterprise","term_group":0,"term_taxonomy_id":42301,"taxonomy":"post_tag","description":"","parent":0,"count":216,"filter":"raw"},{"term_id":768752,"name":"knowledge graph","slug":"knowledge-graph","term_group":0,"term_taxonomy_id":768752,"taxonomy":"post_tag","description":"","parent":0,"count":8,"filter":"raw"},{"term_id":98592,"name":"sync","slug":"sync","term_group":0,"term_taxonomy_id":98592,"taxonomy":"post_tag","description":"","parent":0,"count":8,"filter":"raw"}],"category_data":[{"term_id":738191,"name":"Developers","slug":"developers","term_group":0,"term_taxonomy_id":738191,"taxonomy":"category","description":"","parent":0,"count":436,"filter":"raw"}],"product_data":[{"term_id":36571,"name":"ArcGIS Enterprise","slug":"arcgis-enterprise","term_group":0,"term_taxonomy_id":36571,"taxonomy":"product","description":"","parent":0,"count":997,"filter":"raw"},{"term_id":762232,"name":"ArcGIS Knowledge","slug":"arcgis-knowledge","term_group":0,"term_taxonomy_id":762232,"taxonomy":"product","description":"","parent":36981,"count":33,"filter":"raw"},{"term_id":36861,"name":"ArcGIS REST API","slug":"api-rest","term_group":0,"term_taxonomy_id":36861,"taxonomy":"product","description":"","parent":36601,"count":78,"filter":"raw"}],"primary_product_link":"https:\/\/www.esri.com\/arcgis-blog\/?s=#&products=arcgis-knowledge","_links":{"self":[{"href":"https:\/\/www.esri.com\/arcgis-blog\/wp-json\/wp\/v2\/blog\/2967139","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.esri.com\/arcgis-blog\/wp-json\/wp\/v2\/blog"}],"about":[{"href":"https:\/\/www.esri.com\/arcgis-blog\/wp-json\/wp\/v2\/types\/blog"}],"author":[{"embeddable":true,"href":"https:\/\/www.esri.com\/arcgis-blog\/wp-json\/wp\/v2\/users\/408840"}],"replies":[{"embeddable":true,"href":"https:\/\/www.esri.com\/arcgis-blog\/wp-json\/wp\/v2\/comments?post=2967139"}],"version-history":[{"count":0,"href":"https:\/\/www.esri.com\/arcgis-blog\/wp-json\/wp\/v2\/blog\/2967139\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.esri.com\/arcgis-blog\/wp-json\/wp\/v2\/media?parent=2967139"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.esri.com\/arcgis-blog\/wp-json\/wp\/v2\/categories?post=2967139"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.esri.com\/arcgis-blog\/wp-json\/wp\/v2\/tags?post=2967139"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/www.esri.com\/arcgis-blog\/wp-json\/wp\/v2\/industry?post=2967139"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/www.esri.com\/arcgis-blog\/wp-json\/wp\/v2\/product?post=2967139"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}