When a child replica creates a new feature class, the parent replica should 'receive' it after synchronization

ClintCabanero

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.  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.

AaronGreiner

I would actually like to see the opposite.  When a feature class is added to the parent geodatabse it is then added to the replica and the child database.