Contents Now Platform Custom Business Applications Previous Topic Next Topic Ignore a local change ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Other Share Ignore a local change Ignoring a local change prevents updates to a record from generating new versions in the Local Changes list. About this task An ignored local change always points to the current version for the record. You cannot push ignored records to another instance. Table 1. Local change action list Action Result Ignore a record that has a version queued for push The queued change is deleted Ignore a record that has a version queued for code review The queued change is deleted Pull changes for an ignored record Collision Resolve a collision by taking the parent version There is no longer a local change to ignore Resolve a collision by keeping the local version The ignored change remains on the local instance Procedure Navigate to Team Development > Team Dashboard. Filter the Local Changes list to show only the changes that you want to ignore. For example, filter the list to show all changes in the Default Update Set. Click Ignore All. [Recommended] Review the Ignored list to ensure that the correct changes are ignored. OptionDescription To stop ignoring changes Select the check boxes beside the rows and select Do Not Ignore from the Actions choice list. To stop ignoring changes and add them to the queue instead Select the check boxes beside the rows and select Queue for Push from the Actions choice list. 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 instancesPull 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 DevelopmentPull exceptionsTeam dashboardLimitations on updating records On this page Send Feedback Previous Topic Next Topic
Ignore a local change Ignoring a local change prevents updates to a record from generating new versions in the Local Changes list. About this task An ignored local change always points to the current version for the record. You cannot push ignored records to another instance. Table 1. Local change action list Action Result Ignore a record that has a version queued for push The queued change is deleted Ignore a record that has a version queued for code review The queued change is deleted Pull changes for an ignored record Collision Resolve a collision by taking the parent version There is no longer a local change to ignore Resolve a collision by keeping the local version The ignored change remains on the local instance Procedure Navigate to Team Development > Team Dashboard. Filter the Local Changes list to show only the changes that you want to ignore. For example, filter the list to show all changes in the Default Update Set. Click Ignore All. [Recommended] Review the Ignored list to ensure that the correct changes are ignored. OptionDescription To stop ignoring changes Select the check boxes beside the rows and select Do Not Ignore from the Actions choice list. To stop ignoring changes and add them to the queue instead Select the check boxes beside the rows and select Queue for Push from the Actions choice list. 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 instancesPull 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 DevelopmentPull exceptionsTeam dashboardLimitations on updating records
Ignore a local change Ignoring a local change prevents updates to a record from generating new versions in the Local Changes list. About this task An ignored local change always points to the current version for the record. You cannot push ignored records to another instance. Table 1. Local change action list Action Result Ignore a record that has a version queued for push The queued change is deleted Ignore a record that has a version queued for code review The queued change is deleted Pull changes for an ignored record Collision Resolve a collision by taking the parent version There is no longer a local change to ignore Resolve a collision by keeping the local version The ignored change remains on the local instance Procedure Navigate to Team Development > Team Dashboard. Filter the Local Changes list to show only the changes that you want to ignore. For example, filter the list to show all changes in the Default Update Set. Click Ignore All. [Recommended] Review the Ignored list to ensure that the correct changes are ignored. OptionDescription To stop ignoring changes Select the check boxes beside the rows and select Do Not Ignore from the Actions choice list. To stop ignoring changes and add them to the queue instead Select the check boxes beside the rows and select Queue for Push from the Actions choice list. 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 instancesPull 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 DevelopmentPull exceptionsTeam dashboardLimitations on updating records
