The 1Password Community forums are in read-only mode from Jan 28th - Feb 4th, 2025. Find out more.

Proper way to resolve a group of records with Conflicts Fields

JC54
JC54
Community Member

I started with 1Password at its first version and now I'm on v.5. For quite some time I've noticed some records with a field called "Conflicts" containing really old passwords. I seldom used these and I think the conflicts could be really old. I only recently found the idea of using a Smart Folder to find them all. There are 56 conflicts. Most are old passwords, but some are dates on things like drivers' licenses or birthdates on identities. I sync using Dropbox between at least 4 Macs, and 3 iOS devices. Sync SEEMS to be working in general. I'm using the latest iOS version and version 5 on the Macs.

What's the best way to resolve these and make the Conflicts field go away? Do I just edit the records and delete the conflict fields to specify to all devices that the actual field is correct?


1Password Version: 5.3.2
Extension Version: Not Provided
OS Version: OS X 10.10.2, 10.10.3
Sync Type: Dropbox

Comments

  • Drew_AG
    Drew_AG
    1Password Alumni

    Hi @JC54,

    Normally, conflicts show up when 1Password syncs but is unable to determine which copy of an item has the newer information, so it saves the conflicting info in Conflict fields to ensure that data is not lost. There are a few legitimate reasons why that might happen, but I believe there was a small bug in a previous version which may have caused something like this to happen, so if those Conflict fields have been around for some time, it's possible that bug was the cause.

    If those items still look and behave as intended, and you don't see any data in Conflict fields that should be in other fields (i.e. the normal fields have the correct/current information), then you can simply edit those items and remove the Conflict fields.

    I'm sorry for the trouble! Hopefully this helps, but please let us know if you have more questions about that.

This discussion has been closed.