Several bugs with syncing Bank Accounts

khove

I have encountered a number of bugs when syncing Bank Accounts between Mac and iOS:

• The first general section is resistant to changing field names. I would like to change 'routing number' to 'sort code' and 'SWIFT' to 'BIC/SWIFT' but these changes never stick when syncing and are always reverted.
• The order of items in the general section is also resistant change. I would like to move an item up but it is always pulled back down.
• The section headers do not sync properly. I misnamed a section header, and after changing it on Mac the change does not sync and the only way to fix it is to create a new entry from scratch and make sure to get it right the first time.
• Trying to change any of these text elements at the same time on iOS and Mac to what you want it to be is futile, as each device reverts to what the previous state used to be on the other device respectively.
• The 'type' field (in this case set to 'Checking') sometimes bugs out on iOS and changes the typography, presenting as if it were a revealed password.

Also, it would be great if you could include the feature of rearranging the order of entire sections, not just elements in the sections!

---

1Password Version: 5.4.3 (iOS) / 5.3.2 (Mac)
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Dropbox

littlebobbytables

Hi @khove,

Most of what you're experiencing is due to the fact that the fields and their titles are hardcoded into the actual items. Due to compatibility reasons it isn't possible to alter the agilekeychain format but after we've transitioned to the OPVault it should be something we can address. What you could do in lieu of a better answer is use custom fields. As a Bank Account item isn't one of the special types that we fill with you could ignore certain hardcoded fields with titles you don't like in favour of custom fields with your preferred titles. It's a little hacky but it would work and you can even have custom fields as part of the first section so they don't see too disjointed. Any field without data, even hardcoded ones remain invisible when viewing the item in a read-only state so it won't be the case that your items are full of empty fields. Could that be a workaround for now?

ref: OPI-55

We do have an open request regarding the ability to reorder entire sections and not just fields inside a section. You're right, should you wish to reorder sections it's a pain. I've added your request to the existing one as a vote to see this happen :smile:

ref: OPM-1289

If you have any questions about any of that please do ask!