SPR

Technote

SPR# JSTH5DWK9F - View shows replication conflicts based on cache error. Fixed 3 cases of replication conflicts. The following is a description of the cases:
Open the server based database with "All Documents" view open on Machine A and then edit in designer. Open the same database on Machine B having 8.5 client.
Case 1
Copy the Topic Column and paste it again on Machine A in designer. Save the view. On Machine B, switch to a different view and then come back. Initially used to see ALL Rep Conflicts.
Case2
Delete the newly added Topic column on machine A in the designer. Save the view while the same "All Documents" view is open on machine B. Hit F9 to refresh on Machine B and you will see the column disappearing and the new design changes done on machine A taking place. Go to different view and then come back on "All Documents" view. Initially used to see Rep Conflicts even though it had refreshed correctly before.
Case 3:
Open local discussion database in Notes client. a.Simultaneously open the same local discussion database in Designer client.
b. Copy 'Topic' column and paste it as first column. c. Change the view from 'All Documents' to 'By Author' and back to 'All Documents' view. c. Delete the newly added 'Topic' column in designer and save. d. Change the view from 'All Documents' to 'By Author' and back to 'All Documents' view. Initially use to get Replication Conflicts in view after deleting a column and saving the view.


APAR: LO23640
What is an APAR?


Last Modified on 12/08/2013