Advanced\Custom Field Support

[jkdba]

Add Support for Gettting, Setting, and Adding Custom Fields.

[jkdba]

I am thinking that we use could allow for a hashtable parameter to be passed to the New-KeePassEntry and Update-KeePassEntry that would allow for the user to specify multiple custom properties and values.

@Ninjigen Let me know what you think of this idea.

[Ninjigen]

@jkdba a hashtable seems the easiest way to do this, but we have to make sure the user doesn't try to overload existing properties (UserName, Password, Notes, URL, etc).

[JakeMoe]

I'd love to see support for this as well. We're looking to use KeePass as a backup option for an enterprise database manager, and would be good if I could get some other fields in there.

[YannicNoe]

I also support this. Currently I try to migrate from 1Password to Keepass, because I missed the features of Keepass and I did find a way to bypass our corporate proxy that blocks most cloud services. The export from 1Password is very bad, but i want to also import the history of the entries in Keepaaa. I think there is currently no way to accomplish this with your framework, is there?

[jkdba]

Hi @YannicNoe Can you clarify what you are asking for?

From your comment it appears you want to work with entry history?

If so and its not related to using the custom fields in keepass can you please open a new issue, question or feature request detailing what you are looking for.

[YannicNoe]

Hi @jkdba,
I didn't thought it to the end. Because I did use 1Password for a longer time, i thought that the history is only the password. In Keepass is the complete entry in the history and because of that it is a different thing than custom fields. Thank you for pointing that out.