Pull exceptions Pulling ignores versions when certain conditions occur. Table 1. Pull exceptions table Issue Description Matched an exclusion policy An exclusion policy prevents pulling changes for records matching the policy conditions. The pull identifies the changes but does not include versions for these records. Private properties A private property is excluded from all Update Sets and pulls. Collisions A collision is detected when the pulled version and the current local version both include modifications to the same record. You must resolve all collisions before you can pull. Previously resolved collisions When you resolved a collision by accepting either the pulled version or local version of a record, the pull remembers your decision and accepts the version that you indicated as a "previously resolved collision". Skipped Pulls skip versions where there is a problem with the version record such as a corrupt or missing version. Related TasksApprove 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 changePull a versionPush 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 DevelopmentTeam dashboardLimitations on updating records
Pull exceptions Pulling ignores versions when certain conditions occur. Table 1. Pull exceptions table Issue Description Matched an exclusion policy An exclusion policy prevents pulling changes for records matching the policy conditions. The pull identifies the changes but does not include versions for these records. Private properties A private property is excluded from all Update Sets and pulls. Collisions A collision is detected when the pulled version and the current local version both include modifications to the same record. You must resolve all collisions before you can pull. Previously resolved collisions When you resolved a collision by accepting either the pulled version or local version of a record, the pull remembers your decision and accepts the version that you indicated as a "previously resolved collision". Skipped Pulls skip versions where there is a problem with the version record such as a corrupt or missing version. Related TasksApprove 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 changePull a versionPush 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 DevelopmentTeam dashboardLimitations on updating records
