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


---

# Legacy - Apply remote changes

# Legacy - Apply remote changes {#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

Application developers can pull changes from a linked GIT repository to apply remote
changes to the local instance.

## Antes de Iniciar

Importante:  
Starting with the Xanadu release, the legacy version of ServiceNow Studio is being prepared for future deprecation. It will be hidden and no longer activated on new instances but will continue to be supported. For details on the deprecation process, see the [Deprecation Process \[KB0867184\]](https://support.servicenow.com/kb_view.do?sysparm_article=KB0867184) article in the Now Support Knowledge Base.

Try building and editing apps in the current version of ServiceNow Studio instead. For more information, see [ServiceNow Studio](https://servicenow-prod.fluidtopics.net/HJE5fDsb~bjmVZ9BqGtS8w "ServiceNow Studio provides a unified experience for all ServiceNow development activities, enabling admins and developers to extend base system solutions and create custom apps with ease. Use ServiceNow Studio to build apps and app files with integrated tools, access and edit app metadata in scoped and global apps, and package app changes for deployment, all in one powerful development tool.").

* Role required: admin
* [Legacy - Link an application or application-customization to source control](https://servicenow-prod.fluidtopics.net/2oVB7fYJ7Iq7VapMevRcow "Linking an application or application-customization to source control allows application developers to manage changes from a Git repository.")
{#t_ApplyRemoteChanges__ul_zyd_vlt_s5}

## Procedimento

Navigate to AllSource ControlApply Remote Changes.  
The following operations occur:

* The system fetches the most recent changes from the remote repository.
* The system applies the remote changes to the instance.
* The system identifies any change conflicts requiring resolution.

{#t_ApplyRemoteChanges__ul_p1t_zmt_s5}If there are conflicts, the system displays the Resolve Conflicts window.

Delta loading is enabled by default in sys
properties so your data isn't removed. You can disable this feature if you
want data automatically deleted.  
Nota:  
After a Source Control Apply Remote Changes or other operation, you may encounter the error message: `Skipped loading file *.xml, cannot
parse the xml document, found git merge conflicts tokens`. Make sure that the files in your application do not include values that the Git repository interprets as merge conflict tokens. While these aren't actual conflicts, you should remove them anyway. Examples of these values are:

`>>>>>>>`

`=======`

`<<<<<<<
`

## O que Fazer Depois

Resolve any change conflicts.

