Hi,
I can do a CRUD read operation successfully on a scalar custom poller. Difficulty arise on a tabular one.
I retrieve the following URI from a SWQL query:
swis://SERVER/Orion/Orion.Nodes/NodeID=5/CustomPollerAssignmentOnNode/ID=39/CustomPollerStatus
Then I send it to the server using this address:
https://SERVER:17778/SolarWinds/InformationService/v3/Json/swis://SERVER/Orion/Orion.Nodes/NodeID=5/CustomPollerAssignmentOnNode/ID=39/CustomPollerStatus
It returns with valid data.
But when trying on a tabular one (ie retrieve a single row from the table):
https://SERVER:17778/SolarWinds/InformationService/v3/Json/swis://SERVER/Orion/Orion.Nodes/NodeID=5/CustomPollerAssignmentOnNode/ID=54/CustomPollerStatus/CompressedRowID="1"
I get this message:
{"Message":"Invalid key properties specified for entity Orion.NPM.CustomPollerStatusOnNode.\r\nParameter name: filter","ExceptionType":"System.ArgumentException","FullException":"System.ArgumentException: Invalid key properties specified for entity Orion.NPM.CustomPollerStatusOnNode.\r\nParameter name: filter\r\n at SolarWinds.InformationService.Core.SwisUriLevelInfoParser.ValidateAndResolveFilter(IEntityType entity, SwisUriFilter filter, Boolean isHosted)\r\n at SolarWinds.InformationService.Core.SwisUriLevelInfoParser.Parse(SwisUri uri, ISchema schema)\r\n at SolarWinds.InformationService.Core.SwisUriResolver.CreateFormConsistentUrisResolver(SwisUri representantUri, IEnumerable`1 uris, Boolean queryKeysOnly, IQueryProcessor queryProcessor, IQueryPlanCache queryPlanCache, IQueryExecutionContext context, ISiteEntityLookup siteEntityLookup)\r\n at SolarWinds.InformationService.Core.SwisUriResolver.GetResolver(SwisUri uri, Boolean queryKeysOnly, IQueryProcessor queryProcessor, IQueryPlanCache queryPlanCache, IQueryExecutionContext context, ISiteEntityLookup siteEntityLookup)\r\n at SolarWinds.InformationService.Core.CrudProcessor.Read[T](SwisUri uri, IQueryExecutionContext context)\r\n at SolarWinds.InformationService.Core.InformationService.Read(String uri)"}
Can I assume it's not implemented yet (2019.4), or my URL/URI is wrong?
Christian