All ideas

Showing 582

Partners can create their own displays from shared data

As a company that shares data with our partners, my partners would like the ability to create their own displays from data we share with them SO THAT they can build what they need in a self-service model (and we don't have to build everything for ...

Guest about 2 years ago in Community Data Sharing / Display Sharing 0 No status

3 VOTE

Ad-Hoc Display Sharing

Goal: Replayce the "fax me that display" or "screen shot that display for me". Ability to share a display with an external person on an ad-hoc basis (display not previously shared). The access to the display might be temporary (hours, days, week).

Guest about 2 years ago in Community Data Sharing / Display Sharing 0 No status

3 VOTE

The ability to share the current API Console URI as an encoded URL, just like sharing a trend

The ability share trends as encoded URLs is incredibly useful. Another area where exploration and collaboration can be done is in the API Console, and there I'd love the ability to craft a query URI and then be able to save that query with a sing...

Guest about 2 years ago in Developer Resources / AVEVA™ Data Hub Developer Tools 0 No status

3 VOTE

Read data from multiple streams with a single request

As a developer working on an application that needs to execute a bulk load of MANY separate streams via the OCS REST API, I would like an option to submit a list of streams with start/end index as well as per-stream continuation token, and get raw...

Guest about 2 years ago in Developer Resources / AVEVA™ Data Hub API 0 No status

3 VOTE

Count of a stream

I would like to be able to get only the number of records in a stream. It would be great to be able to do this based on a certain condition.

Guest about 2 years ago in Developer Resources / AVEVA™ Data Hub API 0 No status

3 VOTE

Cascading Security Inheritance Down to Streams and other Objects in a Namespace

If a single namespace is being used to store data from multiple customers or sites, there needs to be a way to propagate security inheritance down to objects (streams, assets, etc.) within the namespace.