PoShKeePass icon indicating copy to clipboard operation
PoShKeePass copied to clipboard

No way to persist an entry's $entry.KPEntry.Strings to database since the breaking changes in Cmdlet naming

Open oleschri opened this issue 2 years ago • 0 comments

With the old Cmdlets Set-KP... I was able to modify an entry including custom values via $kpentry.Strings and persist them to the database. I cannot find a way to do that with the 'new' *-KeePass* Cmdlets.

Update-KeePassEntry only takes the uuid from the passed entry object and updates the values specified in parameters but ignores everything else inside the passed entry object. :(

Old way that worked:

            $entry.Strings.Set('Custom Value 1', (Get-KeePassProtectedString 'ABC'))
            $entry.Strings.Set('Custom Value 2', (Get-KeePassProtectedString '123'))
            $conn.Save($null)
            $conn.Close()

Shouldn't there be an additional variant of Update-KeePassEntry that only takes the databaseprofile etc and a given entry in memory that persist all properties of that entry to the database?

oleschri avatar Nov 19 '21 13:11 oleschri