Legacy - Apply remote changes

  • Rversion finale: Australia
  • Mis à jour 12 mars 2026
  • 1 minute de lecture

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

    Avant de commencer

    Important :
    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] 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.

    Procédure

    Navigate to All > Source Control > Apply 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.
    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.

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

    >>>>>>>

    =======

    <<<<<<<

    Que faire ensuite

    Resolve any change conflicts.