---
sourceDocument: Yokohama Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/application-development

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Pull a version

# Pull a version {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Pulling retrieves versions of customized records from the parent instance and adds
them on the development instance. Pulling does not retrieve any versions for changes made by
system upgrades, but it retrieves all versions for changes made by users, not just the
current version.

## About this task

Pulling retrieves all versions for changes made by users that have not already be pulled onto the development instance, and you cannot choose which versions to pull. The first time you pull from a parent instance, the pull retrieves all versions for changes made by users. Subsequent pulls retrieve the new versions since your last pull. Each pull is recorded in the Push or Pull `[sys_sync_history]` table on the development instance. Historical versions are saved with a state of History.

## Procedure

1. Navigate to AllTeam DevelopmentTeam Dashboard.
2. In the control panel, click Pull.
3. On the completion page, click Show Results.  
   The Push and Pull Versions related list for the Push or Pull form shows the customized records for which versions were retrieved and indicates if any pull exceptions exist.  
4. Resolve any collisions.

*[\>]: and then


