Using a colon inside a custom field name is interpreted by Keeper as a new custom field

[Surowa]

When using, for a custom field named company:customfield:salt and a value of false, using this to set it:
$custom = "company:customfield:salt : true"
Add-KeeperRecord -UpdateOnly -Title $title -Login $login -GeneratePassword -Custom $custom

It creates a new custom field named "company" and a value of "customfield:salt : true"
How to escape this properly?

[tonylanglet]

Hello, are you using comma to separate the different custom fields?

PARAMETER CustomFields
Optional [string], requires the following syntax "key1:value1,key2:value2"...

[Surowa]

Hi, yes, e.g.:
$custom = "company:customfield:salt : true, company:custom:filler : true"
Add-KeeperRecord -UpdateOnly -Title $title -Login $login -GeneratePassword -Custom $custom