Local changes

The Local Changes table tracks customized records that have current versions on the development instance, but not on the parent instance.

You can queue local changes in preparation for a push to the parent instance.

Each development instance maintains a single queue, regardless of who develops or queues the changes. You can ignore local changes that you don’t want to push. For example, you can ignore changes to the color scheme that visually distinguish a development instance from the production instance. You can remove a change from the queue or stop ignoring a change.

Changing the parent instance or reconciling recreates the list of local changes that haven’t been queued or ignored. If you had previously queued or ignored a local change, that designation is maintained.

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’s no longer a local change to ignore
Resolve a collision by keeping the local version	The ignored change remains on the local instance

• Pulling changes
  Developers synchronize their instances to the parent instance by pulling and pushing versions of customized records.
• Pushing changes
  You can push versions of customized records to synchronize your instance to the parent instance.
• Back out a local change
  Back out all local changes and restore the last version reconciled with the parent instance.
• Ignore a local change
  Ignoring a local change helps to prevent a record from generating new versions in the Local Changes list.