Synching changes item layout

Correction: I think originally the software license template had no field groupings, so the meaning of the Company field was ambiguous.

I don't think we can blame this entirely on Dropbox. This weekend I ran an experiment, for the purpose of testing 1Password 7:

1. Installed 1Password 6 on a High Sierra virtual machine, which did not have a) 1Password or b) Dropbox. So this is a clean install.
2. Copied the agilekeychain to the virtual machine, and...
3. Told 1Password 6 to use it.
4. The result was that every entry now had the Company field in the Customer area (or so I thought). So I started moving the Company to the Publisher area.
5. Then I realized that actually what had happened was that the installation had duplicated the Company field: every entry had the Company in two places: Customer and Publisher. (This is with entries that in the source machine were OK.)
6. But remember that I had already moved the Company from Customer to Publisher on about half of the entries, before realizing it was already there. So on these entries, it now has the Company twice in the publisher area: once as the first field and again as the last.
7. OK, so now I tried deleting the extra Company. Here's where it gets really weird: when I deleted the extra Company, it deleted both. That was not a fluke. It did that every single time.

So what we can see here is that there are weird things going on even with synching completely out of the picture. This is simply issues in attempting to edit fields in the license.

Eventually, after a lot of work, I cleaned up all of the licenses, and then upgraded the virtual machine to 1Password 7. I can say that that the upgrade did not make the licenses worse.

I have issues on one machine or the other with every single license I have, which is about 75. The problems are not just with old licenses; I first noticed this with licenses I created a few months ago.

I just ran a test to see if it is possible to correct the data when synching is involved. The answer is no. On any machine, if I correct it there, it screws it up on the receiving end of the sync. If I fix it there, it then corrupts the data again on the first machine.

It is like the sync isn't respecting the field layout. If 1Password is going to permit the user to move fields around, then the arrangement should be maintained on the sync.

Oh man, was this a pain.

1Password 7.1 is out, so time to install the upgrade.

First mistake was to not clean up all the data in one of the computers first; I assumed I could do that in 1Password 7. Wrong. I hadn't counted on that 1Password 7 doesn't let you edit items.

So reinstalled 1Password 6, cleaned up the data.

Then had to struggle to get 1Password 7 to reimport from 1Password 6. First confusion was that File > Import > 1Password 6 won't import from a 1Password 6 keychain or vault; that item really should say 1Password account or something like that. But it is a moot point, because importing from a keychain doesn't work either, even if you first delete the old items you want to replace.

Restoring from a 1Password 6 backup was a challenge too, because the last backup I made wasn't in the list. I suggest that what the conversion should have done is move the 1Password 4 backup folder to the new location and leave an alias behind, so that when you take another backup in 1P6 it shows up in 1P7. (Assuming, of course, that 1Password 6 knows how to follow the alias.)

Anyway, I finally got it to restore the 1P6 backup with the corrected data.

No fool I, on the other Mac I reset the local data, reconnected it to the Dropbox opvault created by 1P7, then did the upgrade. That worked. All done, right?

Then I changed one of the iDevices to use the Dropbox opvault. It immediately uploaded its data to that vault, corrupting all the data again.

So then I had to do it all over again: disable dropbox and delete the data, remove the 1password data from all devices but one, uninstall dropbox from the iDevices, restore the primary computer from the backup again, reestablish sync.

On the secondary computer that took two tries. For some reason the first try only loaded part of the data back from the Dropbox opvault.

But I finally have all the data corrected, in 1Password 7 opvault, on all devices. Only problem is that since 1P7 won't let me edit the entries, if they get out of whack again, I won't be able to fix it.

Your picture says that "1Password 6 ... imports users's entire 1Password 6 for Mac database (all vaults) directly from the .sqllite file". That doesn't work for me. When I select it, I get a prompt "Select your 1Password account and a 1Password database file to import into it.", with an "Import into:" selector. But, the import into selector is greyed out. Nothing happens if I try to click it.

Note that I don't have a 1Password account.

If the intent is that you would use this option to import from a database or opvault, it doesn't work. And, from your description, it doesn't sound like it is intended to import from opvault. So how would you import from an opvault?

It seems to me that you should be able to import from any 1Password data store: opvault, agilekeychain, agilekeychain_zip, 1p4_zip, sqllite database, whatever 1Password 3 used to use. May the import should have one item for all 1Password files.

. . .

By "1Password 7 won't let me edit", I mean that if there is a way to rearrange fields in 1Password 7, I can't find it. And remember, the entire point to this post was that 1Password synching was messing with the fields: moving them to different sections, duplicating them, moving them to different positions in the section -- all things that in order to correct, you need to be above to move the field.

The funny thing is that there are support posts that reply to people asking why they can't move sections with "you can't move sections but you can move fields". Now you can't even do that.

That is the most disappointing thing about 1Password 7.

I did realize that I may be able to use 1Password 6 for editing going forward, as long as I'm very, very careful: Start 1P6, reset its data, reload from the Dropbox opvault, make change, then turn off sync. The key is to ensure it never syncs data from an old local database back to the dropbox opvault.

The field drag handles are gone from Software License items in 1Password 7, as is the widget for deleting fields.