lordmilko

Hi @terminatorbs, I've managed to successfully reproduce this issue In the *DeviceToDestination* parameter set * the `-DestinationId` is positionally parameter 0, * `-Name` is parameter 1 * and `-Host` is...

Note that you can work around this issue for now by explicitly specifying the names of the parameters you're trying to use ```powershell Get-Device -Id 45503 | Clone-Object -DestinationId 45502...

Correction to my earlier message, this is actually as a result of how PowerShell treats wildcards. Typically when people talk about "wildcard characters" in PowerShell are usually referring to the...

I've had a look into this a little further and have found a way PrtgAPI may be able to work around this in a future release; for the meantime however...

I'm unable to reproduce this issue. Are you able to confirm what version of PrtgAPI you're running? Has the above screenshot been manipulated, or is it the output of a...

Hi @fab37100, I would imagine in order to do this you would need to use the `Get-DeviceTemplate` cmdlet to retrieve the template you want to use, and then specify a...

Hi @paulkva, Supporting the creation of additional object types (including Notification Actions) is something I've considered previously, however for most of these types (such as Schedules and Notification Actions) these...

Are you able to advise what you mean by *expose a generic `CloneObject` method*? I was successfully able to clone a Notification Action using the following code ```c# var newId...

I'm not sure how you're getting a newID of `3`; when I do that against PRTG 19.2 with PrtgAPI 0.9.6 I get an ID of `2096`; the known issue listed...

EDIT: nevermind, I see you noted that the issue was resolved in PrtgAPI 0.9.6. Yes, this would be related to the > Fixed CloneObject failing to parse ID of created...