Is there a process to clean up / eliminate duplicate "Purchase Date" fields in software licenses?
I'm seeing corruption in purchase date on multiple entries for software assets stored in my main vault. It looks like dates +1 day are being added on most if not all entries. Some have 12 or more "purchases"
Is this a known issue, or should I reach out to support to further investigate?
I'm on 1Password Version 5.3 (530029) Mac App Store trying to clean things up, but I do beta test iOS and Mac (previously) so the data contamination / corruption could be elsewhere.
1Password Version: 5.3
Extension Version: 4.3.1
OS Version: 10.11 and iOS 8 and iOS 9
Sync Type: iCloud
Referrer: forum-search:software license purchase date
Comments
-
I don't know that there is an automated way to take care of all of those at once, but if you are ready to do it record-by-record, are you aware that you can delete entire fields by clicking on the red encircled minus sign next to each? Like this, from the demo vault:
No insult intended if this is already obvious to you.
The duplications strike me as odd. I've been running the betas for quite awhile and don't have similar entires in my records for software licenses.
0 -
Greetings @bmike,
Are the majority of these fields stored in a section titled Conflicts by any chance? I could kind of understand that if they are and if you need to remove an entire section you can do so in the same way you would remove just a single field. It might suggest something isn't quite right with syncing but we'll wait to hear if my suspicion (above) is correct or not.
0 -
Greetings @littlebobbytables - None of these show up as "Merge Conflicts"
@hawkmoth - Deleting one or two generally doesn't work as they revive themselves. Undead date fields :(
0 -
Hello @bmike,
Okay, that's very strange.
Can you do something for us please.
- Make a note of the day/time.
- Create a brand new Software Licence item and set the field like you have in the broken item.
- Select one of the misbehaving items and delete all but one of the fields.
- Once the fields have returned, can you create a diagnostic report for us please along with any observations on the test item you created in step 2. and the timestamp you made a note of in step 1. The timestamp will hopefully allow us to narrow down the search.
Here is a link on how to create the diagnostic report.
Please do not post your Diagnostics Report in the forums
The email address you will want to use is support+forum@agilebits.com.
When sending the diagnostic report to the address above it would help immensely if you could include a link to this thread and your forum handle so we can connect the two.
Once you've sent the report a post here with the ticket ID will help us to keep an eye out for it. Hopefully there will be something in the log that might indicate what this issue is.
Sorry about all of this. Conflicts I could understand but it sounds like you're describing zombie-like fields which is a lot more unusual.
0 -
Will do. For my notes, 11:00 AM today is the start time. I'll clean things up. It turns out the first dates are all wrong. The last entry seems to be categorically correct. Also, most of the errors are for entries before 2013 so the bits have had some time to stew, ferment and rot. :-(
Will update again with the diagnostics if/when things fall apart again.
0 -
Keep us updated @bmike :smile: From the some of the earlier posts it sounds like the fields returned pretty soon after deletion so if there is an issue hopefully it will make itself present soon.
0 -
So far, so good @littlebobbytables - I can conclusively say iCloud sync was pathologically behind on the Mac I chose to use for cleanup, so that seems to be the main reason why things I cleaned up weren't.
After nuking that iCloud setting, deleting everything and getting a clean reload of the iCloud data overnight - things look better for now. I'll update again if I can catch this peculiar issue and send the logs at that time.
0
