<?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>idea When a child replica creates a new feature class, the parent replica should 'receive' it after synchronization in Data Management Ideas</title>
    <link>https://community.esri.com/t5/data-management-ideas/when-a-child-replica-creates-a-new-feature-class/idi-p/955158</link>
    <description>&lt;P&gt;As I understand the current deployment, when updating existing data in a child replica, or deleting existing data in a child replica, these types of changes are correctly synchonized with a parent replica. &amp;nbsp;However, if a child replica creates a new feature class, and you synchronize with the parent, the parent does not get the added feature class out of the box without some clumsy work-arounds.&lt;/P&gt;&lt;!--  content transformation source ID: 0873000000086yl  --&gt;</description>
    <pubDate>Mon, 29 Aug 2022 23:40:53 GMT</pubDate>
    <dc:creator>ClintCabanero</dc:creator>
    <dc:date>2022-08-29T23:40:53Z</dc:date>
    <item>
      <title>When a child replica creates a new feature class, the parent replica should 'receive' it after synchronization</title>
      <link>https://community.esri.com/t5/data-management-ideas/when-a-child-replica-creates-a-new-feature-class/idi-p/955158</link>
      <description>&lt;P&gt;As I understand the current deployment, when updating existing data in a child replica, or deleting existing data in a child replica, these types of changes are correctly synchonized with a parent replica. &amp;nbsp;However, if a child replica creates a new feature class, and you synchronize with the parent, the parent does not get the added feature class out of the box without some clumsy work-arounds.&lt;/P&gt;&lt;!--  content transformation source ID: 0873000000086yl  --&gt;</description>
      <pubDate>Mon, 29 Aug 2022 23:40:53 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/when-a-child-replica-creates-a-new-feature-class/idi-p/955158</guid>
      <dc:creator>ClintCabanero</dc:creator>
      <dc:date>2022-08-29T23:40:53Z</dc:date>
    </item>
    <item>
      <title>Re: When a child replica creates a new feature class, the parent replica should 'receive' it after synchronization</title>
      <link>https://community.esri.com/t5/data-management-ideas/when-a-child-replica-creates-a-new-feature-class/idc-p/955159#M1087</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;I would actually like to see the opposite.&amp;nbsp; When a feature class is added to the parent geodatabse it is then added to the replica and the child database.

&lt;!-- content transformation source ID: 00a30000006z9Qg --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 May 2010 17:26:05 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/when-a-child-replica-creates-a-new-feature-class/idc-p/955159#M1087</guid>
      <dc:creator>AaronGreiner</dc:creator>
      <dc:date>2010-05-11T17:26:05Z</dc:date>
    </item>
    <item>
      <title>Re: When a child replica creates a new feature class, the parent replica should 'receive' it after synchronization</title>
      <link>https://community.esri.com/t5/data-management-ideas/when-a-child-replica-creates-a-new-feature-class/idc-p/955160#M1088</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think this idea is more reasonable &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Sep 2017 21:54:17 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/when-a-child-replica-creates-a-new-feature-class/idc-p/955160#M1088</guid>
      <dc:creator>KipoKipo</dc:creator>
      <dc:date>2017-09-01T21:54:17Z</dc:date>
    </item>
  </channel>
</rss>

