Contents Custom Application Development Previous Topic Next Topic Pull a version Subscribe Log in to subscribe to topics and get notified when content changes. ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Share Pull a version 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 taskPulling 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 Navigate to Team Development > Team Dashboard. In the control panel, click Pull. On the completion page, click Show Results. The Push or Pull form opens. The Push and Pull Versions related list shows the customized records for which versions were retrieved and indicates if any pull exceptions exist. Resolve any collisions. Related TasksTeam Development processApprove or reject a pushBack out a local changeCancel a code review requestChange the parent instanceCheck the review status of a pushed changeCompare a pushed version to a local versionCompare to peer instancesIgnore a local changePush a versionBack out a pushQueue a local change for a pushReconcile changesResolve a collision in Team DevelopmentResolve multiple collisionsRelated ConceptsLocal changesLocal change listsRelated ReferenceWhen to use Team DevelopmentPull exceptionsTeam dashboardLimitations on updating records On this page Send Feedback Previous Topic Next Topic
Pull a version 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 taskPulling 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 Navigate to Team Development > Team Dashboard. In the control panel, click Pull. On the completion page, click Show Results. The Push or Pull form opens. The Push and Pull Versions related list shows the customized records for which versions were retrieved and indicates if any pull exceptions exist. Resolve any collisions. Related TasksTeam Development processApprove or reject a pushBack out a local changeCancel a code review requestChange the parent instanceCheck the review status of a pushed changeCompare a pushed version to a local versionCompare to peer instancesIgnore a local changePush a versionBack out a pushQueue a local change for a pushReconcile changesResolve a collision in Team DevelopmentResolve multiple collisionsRelated ConceptsLocal changesLocal change listsRelated ReferenceWhen to use Team DevelopmentPull exceptionsTeam dashboardLimitations on updating records
Pull a version 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 taskPulling 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 Navigate to Team Development > Team Dashboard. In the control panel, click Pull. On the completion page, click Show Results. The Push or Pull form opens. The Push and Pull Versions related list shows the customized records for which versions were retrieved and indicates if any pull exceptions exist. Resolve any collisions. Related TasksTeam Development processApprove or reject a pushBack out a local changeCancel a code review requestChange the parent instanceCheck the review status of a pushed changeCompare a pushed version to a local versionCompare to peer instancesIgnore a local changePush a versionBack out a pushQueue a local change for a pushReconcile changesResolve a collision in Team DevelopmentResolve multiple collisionsRelated ConceptsLocal changesLocal change listsRelated ReferenceWhen to use Team DevelopmentPull exceptionsTeam dashboardLimitations on updating records
