I created a few custom fields and assigned values to them, for a number of entries. In hindsight, I realize I should have chosen different names for these fields (in a different language, for example). Is there a way to rename them all in a few turns or do I have to go to each entry and each custom field and rename each of them manually? I want to rename custom fields for all entries that use them.
Last edit: Samir 2022-02-17
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is there no way to add a new custom field without assigning it to an entry? I can't find any option that would allow me to do that. If I want to add a custom field, I have to have an existing entry, and add it via the Edit Entry dialog. I suspect that this is the reason why custom fields can't be updated across all entries that use them.
To me this is counter-intuitive and counter-productive. It tells me that custom fields should be used with reservation and only in very niche use-cases. It's a pity, because adding custom fields for properties that are common across all or many entries creates structure and is rather more useful than pasting in those details in the notes area/field.
Last edit: Samir 2022-02-17
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is there no way to add a new custom field without assigning it to an entry?
Field names are not stored in a separate dictionary in KeePass, they exist in the entries themselves.
Changing this behaviour would require a change to the KeePass database format.
cheers, Paul
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Even though the Fields Admin Console plugin is a bit dated, it worked out nicely for me. Thank you!
The most recent version was released in 2014 and made for KeePass 2.09. In addition, the description says it has been tested on 2.28 as well. I can report that it works in 2.50 as well. I have not had any issues thus far (I have only used it to bulk rename field names).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You say that like it's a bad thing... 😉
(I take it as a sign of stability instead - nothing has happened to KeePass or to Windows itself that has invalidated the old work.)
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Oh I know. I do like it for this reason. I was going to say something about that but I didn't find the right words. How do you say in English... like you might say about wine... it is well dated? I'm sure you know what I mean.
Truth to be told, I really appreciate IT systems that stand the test of time. Nothing really lasts forever, but more often than not, breaking changes in software are introduced for bad (senseless) reasons, in my experience.
You say "old work". I want to emphasize that. A lot of time and hard work goes into making and maintaining software. Ideally, it should not be invalidated overnight. If something is worth your time and effort, make sure you build something that lasts. Something like the KeePass project.
So yeah... old doesn't necessarily mean something bad. Not in my book. Thanks for inviting me to elaborate on that.
Last edit: Samir 2022-02-20
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I created a few custom fields and assigned values to them, for a number of entries. In hindsight, I realize I should have chosen different names for these fields (in a different language, for example). Is there a way to rename them all in a few turns or do I have to go to each entry and each custom field and rename each of them manually? I want to rename custom fields for all entries that use them.
Last edit: Samir 2022-02-17
Is there no way to add a new custom field without assigning it to an entry? I can't find any option that would allow me to do that. If I want to add a custom field, I have to have an existing entry, and add it via the Edit Entry dialog. I suspect that this is the reason why custom fields can't be updated across all entries that use them.
To me this is counter-intuitive and counter-productive. It tells me that custom fields should be used with reservation and only in very niche use-cases. It's a pity, because adding custom fields for properties that are common across all or many entries creates structure and is rather more useful than pasting in those details in the notes area/field.
Last edit: Samir 2022-02-17
Have a look at the KPFieldsAdminConsole plugin:
https://keepass.info/plugins.html#kpfieldsadmin
Best regards,
Dominik
Field names are not stored in a separate dictionary in KeePass, they exist in the entries themselves.
Changing this behaviour would require a change to the KeePass database format.
cheers, Paul
Even though the Fields Admin Console plugin is a bit dated, it worked out nicely for me. Thank you!
The most recent version was released in 2014 and made for KeePass 2.09. In addition, the description says it has been tested on 2.28 as well. I can report that it works in 2.50 as well. I have not had any issues thus far (I have only used it to bulk rename field names).
You say that like it's a bad thing... 😉
(I take it as a sign of stability instead - nothing has happened to KeePass or to Windows itself that has invalidated the old work.)
Oh I know. I do like it for this reason. I was going to say something about that but I didn't find the right words. How do you say in English... like you might say about wine... it is well dated? I'm sure you know what I mean.
Truth to be told, I really appreciate IT systems that stand the test of time. Nothing really lasts forever, but more often than not, breaking changes in software are introduced for bad (senseless) reasons, in my experience.
You say "old work". I want to emphasize that. A lot of time and hard work goes into making and maintaining software. Ideally, it should not be invalidated overnight. If something is worth your time and effort, make sure you build something that lasts. Something like the KeePass project.
So yeah... old doesn't necessarily mean something bad. Not in my book. Thanks for inviting me to elaborate on that.
Last edit: Samir 2022-02-20