You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... if correct then the most useful export/import method (i.e. Buttercup CSV) seems to export all old vault custom fields (i.e. from every entry) to each new entry in the new vault
I was going to report the same issue. After an import (using Buttercup csv format) it should give the same result than before export.
Above : before export
Below : after import
As you can see on screenshot the entry type has been lost (Website => Login) and "Url" field is now considered as a custom field named "url".
Furthermore, Buttercup should provide an easy way to change vault password.
The extra fields are present in the CSV as it's a matrix - there's not really a nicer way to render all specified fields in a matrix besides listing out all of the used property names along the X axis (columns). This is expected. It should result in the same structure upon import, so for that I'll move this issue to the importer so it can be dealt with.
Hi!
Thanks, as always, for software
I have a use case for you...
Tonight I wanted to update my vault password
It seems this is non-trivial
I presume I have to:
... if correct then the most useful export/import method (i.e. Buttercup CSV) seems to export all old vault custom fields (i.e. from every entry) to each new entry in the new vault
For example:
Vault
Entry 1
Entry 2
CSV (export)
Is this expected behaviour?
I would expect, by default, if the entry has no field value then don't show the field..?
IMO the export/import feature is currently redundant/unusable as I wouldn't want tons of superfluous/empty fields in all my entries 😕
Hope this is useful and to hear back
Sincerely
PS if this is, indeed, a problem then I suppose it's higher priority than solving my original use case 🤪
The text was updated successfully, but these errors were encountered: