Hi Benedikt,
this is actually by design. The custom properties are actually stored (encoded) in one data property, that's why it's not possible to make bulk-changes without losing previous properties.
For V5 we have some improvements around the PowerShell cmdlets on the roadmap which will improve script based access to custom properties.
Regards,
Stefan
Allright, thanks for clarification
Benedikt Blömer
Hi there,
I dont know if this is specific to the new Beta, but when I am bulk-editing custom properties on my connections it will remove any custom property already in place at a connection.
It should not overwrite the whole custom properties of a connection but add the new ones to it, am I right?
regards,
Benedikt