Schneider Electric support forum about SmartConnector applications for integration of other building management systems (BMS) into EcoStruxure Building Operation.
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
2017-05-0406:30 AM
GET /Trends using RESTfull EWS Gateway
Hi All,
We have successfully pulled data from some logs in a test environment but now need to go into this a bit deeper.
I know the GET/Trends is not supported in SoapEwsRestProvider but this is exactly what we need to do next. We want to get a list of trend logs in the system.
Apart from the GET/Trends which is not supported, is there any other way we can do this? Currently we run a query in SQL to get all the trends but then manually have to add them to the code.
Also will future versions support this? Where is the limitation?
Link copied. Please paste this link to share this article on your social media post.
2017-05-0406:47 AM
Petri,
The RESTful EWS Gateway API was designed in a provider agnostic manner. As a result, it was known that not all Providers would be able to support all methods.
The limitation for the SoapEwsRestProvider is that it uses EWS under the covers and EWS doesn't allow a way to "get all Trend Logs in a system" in one call. The only workaround is to browse the object tree yourself. As you can imagine this could be a very chatty endeavor and that is why it wasn't considered as a workaround for the provider. In contrast, the MongooseEWsRestProvider has direct DB access to its data source so it can easily support this method.
Current development on a native SBO provider should alleviate this restriction. This will of course be a different provider, but it will use the exact same API.