---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/application-development

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Select the parent instance

# Select the parent instance {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

An instance can have multiple peer instances but only one parent
instance.

## Antes de Iniciar

Role required: none

## Por Que e Quando Desempenhar Esta Tarefa

The parent instance is the only instance you can pull changes from and push changes
to.

The parent instance must be on the same release family as the local instance. For
example, a development instance on the Geneva release family must have a parent
instance also on the Geneva release family. If you select a parent from a different
release family, the Team Development dashboard displays an error message and
prevents you from pulling changes and reconciling. If you select a parent from a
different patch release, the dashboard displays a warning message but allows you to
pull changes and reconcile.  
Do not use Team Development with production or test instances.

* Do not use a test or production instance as the parent instance in Team Development.
* Do not make any instance the parent of a production instance.
* Production instances should never have a parent.
When you back out a change on a Team Development instance, it backs out the change all the way back down the chain, including undoing the work on the source instance. This behavior can cause major problems on test and production instances.

## Procedimento

1. Navigate to AllTeam DevelopmentTeam Dashboard. {#t_SelectTheParentInstance__step-1-navigate-team-dashboard}
{#t_SelectTheParentInstance__step-1-navigate-team-dashboard}
2. In the control panel, click the appropriate link:  
   {#t_SelectTheParentInstance__table_bfc_1cb_bq__entry__2}

   | Option | Description |
   |-|-|
   | Use \<instance name and URL\> | Selects the most recently defined remote instance as the parent instance. |
   | Select a different instance | Opens a dialog box where you can select another remote instance or define a new remote instance. |
   | Register a new instance or List all remote instances | Opens the remote instance form or list, where you can define a new remote instance. These options are available when no remote instances are defined. |
   [Tabela 1. Team dashboard control panel options]

   {#t_SelectTheParentInstance__table_bfc_1cb_bq}  
   {#t_SelectTheParentInstance__step-2-click-link}
{#t_SelectTheParentInstance__step-2-click-link}
3. If you defined a new remote instance in step 2, repeat [step 1](https://servicenow-prod.fluidtopics.net/s2EDUVaMvimwpzOh9YfRmA#t_SelectTheParentInstance__step-1-navigate-team-dashboard) through [step
   2](https://servicenow-prod.fluidtopics.net/s2EDUVaMvimwpzOh9YfRmA#t_SelectTheParentInstance__step-2-click-link) and select the remote instance you defined.  
   The system initiates a reconcile, which compares the local instance to the
   parent. It then generates the list of local changes and calculates the
   number of changes that are ready to pull from the parent. The reconcile also
   validates the instance versions.
4. Pull all changes from the parent instance if both instances are in the same release family.  
   Nota:  
   The parent instance is saved in the glide.apps.hub.current system property.