Hi Tony, I am fully convinced what your doing works for you, and indeed in the SN-environment the queries work for me also, but for me in a non-SN-environment, for some reason, only a few of the parameters seem to work. I think the problem is something other than 'syntax.'
[hypothetically:] Could I somehow create a REST-API that would limit the possible parameters?
Could I make a new-parameter, say 'limit', that users could use?
[Current issue] Attempt:
I made a new GET-tab and also cleared all cookies: Did not help, but eagerly tried them out.
I took postman's code for powershell, which gave me: (below).
It seems whatever constellation I try,
1. only the limit and offset parameters work.
2. The sysparm_fields, sysparm_query don't have any effect and
3. sysparm_limit doesn't work either. [as long as 'limit' works, I'm ok]
ps1:
$headers = New-Object "System.Collections.Generic.Dictionary[[String],[String]]"
$headers.Add("Authorization", "Basic TopSecretPassword")
$URL0 = 'https://[myCO]/api/snc/v2/co_rest_api/[guid]/GetCostCenterList?sysparm_limit=2&offset=10'
$URL0 = 'https://[myCo].service-now.com/api/snc/v2/co_rest_api/[guid]/[table]?limit=2&offset=10'
$URL1 = '&sysparm_fields=sys_updated_on%2Csys_id'
$URL1 = '&sysparm_fields=sys_updated_on,sys_id'
$URL2 = ''
$URL1 = '&fields=sys_updated_on,sys_id'
#$URL2 = '&sysparm_query:sys_updated_on>=2020-01-31 07:00:00^ORDERBYsys_updated_on'
#$URL2 = '&sysparm_query:sys_updated_on>=2020-01-31 07:00:00'
#$URL3 = '^ORDERBYsys_updated_on'
$URL3 = ''
$url = $URL0 + $URL1 + $URL2 + $URL3
$response = Invoke-RestMethod $url -Method 'GET' -Headers $headers -Body $body
{
"result": [
{
"u_telecommunication": "0",
"u_outsourced_service": "0",
"sys_created_on": "2019-05-17 13:04:18",
"sys_updated_on": "2019-09-30 03:22:16",
"sys_id": "[guid]",
...[~40 fields]
},
...
]
}
The url here is
https://....?limit=2&offset=10&fields=sys_updated_on,sys_id
