Replies: 1 comment
-
Unfortunately not something that is able to be replicated here, could it be an issue in your local environment or platform configuration? Consider following the troubleshooting / manual api testing instructions with the example code provided here to see if the same issue happens when not using the psPAS module. #after New-PASSession
$ThisSession = Get-PASSession
$AccountID = 21_4
$Method = "PATCH"
$UrlPath = "api/Accounts/$AccountID"
$Body = ConvertTo-Json @(@{"op" = "add";"path" = "newdescription";"value" = "your new description"})
$Request = @{
"Method" = $Method
"Uri" = "$($ThisSession.BaseUri)/$UrlPath"
"Body" = $Body
"WebSession" = $ThisSession.WebSession
"ContentType" = "application/json"
}
Invoke-RestMethod @Request Hope this helps |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
using the PSPAS modules, I try to add/replace/remove custom properties.
However, I can't get it to work with adding a custom propertie; I constantly get a "Invoke-PASRestMethod : [400] Invalid Input Request. Reason: Object reference not set to an instance of an object." error.
for instance....

base account:
when I use operator add or replace it works ok if the propertie is already there:

when I after that remove the propertie and try to re-add it, it fails:

what am I doing wrong to get the custom propertie added via PSPAS?
in above example of updating, I added the propertie manually via the PVWA by editing the custom field in the account properties.
note:
EPV 12.2
PVWA 12.2
and custom property "newdescription" added and available via file categories within PAClient
Beta Was this translation helpful? Give feedback.
All reactions