Review conflicts detected during a refresh
When you use the Refresh function, some of the received changes might be to items that you have changed in the image. If you have not sent your changes to the SDB, your changes are overwritten; after the refresh operation completes, the item's properties and relationships in the image will match the data held in the SDB. The Conflicts detected in SDB Refresh at transaction window describes the conflict that existed between data in your image and data in the SDB, prior to the refresh.
About this task: A conflict scenario can occur when multiple users modify the properties or relationships of the same item. For example, another user might change the staff member that is allocated to an activity, then send their changes to the SDB. At the same time, you might change the same activity's location. When you click Refresh, your change is overwritten, and the staff change made by the other user is applied to your image. The Conflicts detected in SDB Refresh at transaction window appears and describes those changes.
The data in the Conflicts detected in SDB Refresh at transaction window is presented as a set of nested tables. You can click the + and - icons to expand and collapse tables in the window; doing so can help you browse the information more easily.
To review the changes made to items that you had modified, follow these steps:
- Identify which items have changed. Each row in the outermost table corresponds to an item; the tables nested in that row tell you which data changed. By default, each row contains the Object Type, Name, and Host Key of each changed item.
- For each item, identify the properties and relationships that were changed. Within each row in the outermost table, a nested Change Details table contains a row for each property and relationship that changed. For example, the Property column of the Change Details table might tell you that the Scheduled Staff of an activity was changed.
- For each change to a property or relationship, review the change that occurred. Within each row in the Change Details table, a nested table contains the change to data. For example, a row might contain a Relationship Changes table in the Scheduled Staff row; the table tells you which staff member was removed, and which staff member was added.
Copyright © Scientia Ltd. 2016