Using Soap/Rest and Sbo/Rest endpoints to explore SBO

[Anonymous user]

I'm trying to figure out how to programmatically explore their ES (for example), and collect valid Ids for items (so that users can explore a directory tree of their SBO and pick which items they want polled by my client)

What I've noticed, is that if I'm exploring an Alarm, it has two identities, 00/<path>, and 02/<path>, and I can request GET Containers/00%2F<path>/Children, and this will list its property items, which each have their own id.

This seems to work fine with the Soap/Rest endpoint, but the Sbo/Rest endpoint responds with 404 error if I request Get Containers/%2F<path>/Children, and unlike the Soap version, I can't modify the id to specify to use the container id.

Is there another way to get to the property items of an alarm? (I'm trying to keep the code as general purpose as possible, so I'd rather not just assume certain properties are always there just because the item is an Alarm.)

[JeffBowman]

Hi Josh,

The way it works today is as you mentioned.

Since the SboEwsRestProvider is using a different mechanism behind the scenes there are some instances where the behavior isn't exactly the same as the SoapEwsRestProvider. We have tried to make these as consistent as possible, in this case, it seems as though we have missed this feature with the implementation of the SboEwsRestProvider. I have entered it as an bug and we will be taking a look at it and keep you updated!

Regards,

-Jeff

[Anonymous user]

Thanks! looking forward to an update then

[JeffBowman]

Hi Josh,

I looked into implementing this, however it seems that the with the mechanism we use behind the scenes, there is no easy way to do this. That said, although I agree the behavior should be consistent. I think this feature in the SboEwsRestProvider will likely need to be done in a later release.

I will keep you updated!

Regards,

-Jeff