PI Developer Technologies
Welcome to the
PI Developer Technologies
feedback page!
This forum covers the PI AF SDK, PI Web API, PI OPC DA and HDA Servers, and the PI SQL family. We created this forum to hear your ideas, feature suggestions and feedback. Please suggest your most important features and design change ideas on this site, and vote for your favorite ideas.
Please note that your ideas and comments posted here are visible to all other users.
- For bugs, please open a case with OSIsoft Tech Support through myOSIsoft Customer Portal (https://my.osisoft.com) instead of sharing them on this site.
- For documentation feedback and bugs, please report to documentation@osisoft.com instead of sharing them on this site.
-
Be able to use RTQP to access PI Points and Config strings (DA Directly)
Be able to use RTQP to access PI Points and Config strings (DA Directly)
Use case:
create a dashboard that lets me know the amount of bad data (tags) mapped to our AF.(eg. “Bad Input”, “Calc Failed”, etc)
Our system has numerous tags and it is impossible to monitor them one by one.
The RTQP engine has allowed us to query massive amount of AF Attributes to get their current values easily.
Some AF attributes have been excluded in our system. For that case, we are not interested whether or not the values are bad.
Hence I would like…
40 votes -
PI SQL Client to make use of the RecordedValue method and Retrieval Modes for the GetValue transposed function
When making use of the GetValue transposed function when creating a new Template specific Data Model, we can see that under the hood it makes us of the AF SDK call AFData.InterpolatedValue method to capture the data at a specified timestamp provided in the transposed function. This method does make use of any Retrieval Modes.
It would be good for this GetValue transposed function to make use under the hood of the AF SDK call AFData.RecordedValue method instead since this method offers the possibility of using Retrieval Modes like "AtOrBefore" which is really useful to capture the last archived value…
18 votes -
Add data reference impersonation for value retrievals
When retrieving values for attributes, impersonating the user can enable the user of security at the data source level. For example, with a PI Point Data Reference attribute, it could allow the user's authorization to be user at the data archive rather than the PI SQL DAS (RTQP) service account doing the data retrieval.
15 votes -
Include overridden attributes of derived templates in Event Frame View with PI SQL DAS (RTQP)
When you create a template-specific event view, event frames based on derived templates are also returned. However, attributes which are overridden in the derived template return empty. This means more complicated queries using UNION ALL must be used.
As a user, when I use a derived template with an overridden attribute, it is often because I need to change the way that attribute is calculated in a subset of cases. However, I still want to be able to create a view easily for all of this data.
For example, I have a "Batch" template with "Pounds Produced". However, for a…
11 votes -
Provide a PI SQL Commander Lite Standalone Download
Currently, PI SQL Commander Lite is bundled with PI SQL Client, PI OLEDB Enterprise, and PI ODBC Driver.
It is a very useful tool for PI OLEDB Provider, which does not bundle it. To use it, another provider needs to be installed to obtain PI SQL Commander Lite indirectly.
The version of PI SQL Commander Lite that is bundled with each provider is the latest version of PI SQL Commander Lite at the time of the provider's release. This means that the latest versions of each provider could have different versions of PI SQL Commander Lite bundled with them.
Manageability…
6 votes -
Enable SSO on PI SQL client to connect and authenticate to PI SQL DAS(RTQP engine)
Currently PI SQL clients only support Kerberos & basic authentication. Enabling SSO on PI SQL client to connect and authenticate to PI SQL DAS(RTQP engine) would make PI data accessible from anywhere.
5 votes -
Return row number from PI SQL Client calls
It would be useful to be able to access a specific row from a PI SQL Client call. For example if I query muiltiple attributes indicating some KPI ordered from highest to lowest returning 1000 rows, I might want to show only the top 10. The TOP function is supported in SQL Client, but the Table Lookup DR in AF only allows you to find the first row.
It would be useful if either the row number, 1..n, was returned or the table lookup DR would allow you to pick a specific row. This would then allow you to show…
4 votes -
Add support for nested SELECT statements in PI SQL (RTQP)
The current version of PI DAS (RTQP Engine) does not support nested SELECT statements. This is a rather dire oversight, given that the older PI OLEDB Enterprise query engine does support nested SELECT statements.
A very useful application of nested SELECT could be to centralise some arguments in SQL Views of their own, such as calculated start and end dates of time ranges.
3 votes -
Add support for local variables in PI SQL (RTQP)
The current version of PI DAS (RTQP Engine) does not support local variables. It causes rather clumsy constructs in some instances.
2 votes -
Get AF Server Name and AF Database Name in PI SQL DAS (RTQP)
As a PI Applications Developer, I need to be able to retrieve the name of the current AF Server and Current AF Database in the PI SQL DAS (RTQP). This information was available in PI OLEDB Enterprise’s [System].[Connection].[ConnectionProperty] and [System].[Connection].[ConnectionStatus] tables. I would like it to be in PI SQL DAS (RTQP) as well.
2 votes -
2 votes
-
Add RTQP PI SQL support for default value of function parameter
The current version of PI DAS (RTQP Engine) does not support the definition of default values for table-valued function parameters. This is a rather bleak omission, in my view. For example, the following will fail to create the table-valued function:
CREATE FUNCTION [MOMS].[fact].[getInstrumentOperationalDataSummaries]
(
@StartTime DateTime,
@EndTime DateTime,
@TimeStep TimePeriod,
@TimeType String = 'MostRecentValue'
)
AS
SELECT i.*
,s.ValueFROM MOMS.dim.InstrumentsBase i
CROSS APPLY [MOMS].[fact].[Instrument Base Template_GetSummaries]
(
i.ElementID, --Element ID
@StartTime, --Start Time
@EndTime, --End Time
@TimeStep, --Time Step
@TimeType --Time Type
) sIt should not. It is most reasonable to wish to provide a default value for…
1 vote -
Add RTQP PI SQL support for parameter type cast
PI DAS (RTQP Engine) 2018 SP3 Patch 1 lacks support for type casting input parameters of a table valued function. For example. this simple example fails to create a table valued function:
CREATE FUNCTION [MOMS].[fact].[getInstrumentOperationalDataStringOverload]
(
@StartTimeIn String,
@EndTimeIn String,
@TimeStepIn String
)
AS
SELECT * FROM MOMS.fact.getInstrumentOperationalData(
CAST(@StartTimeIn As DateTime)
,CAST(@EndTimeIn As DateTime)
,CAST(@TimeStepIn As TimePeriod)
)The following example fails in similar fashion:
CREATE FUNCTION [MOMS].[fact].[getInstrumentOperationalDataStringOverload]
(
@StartTimeIn String,
@EndTimeIn String,
@TimeStepIn String
)
AS
SELECT * FROM MOMS.fact.getInstrumentOperationalData(
DateTime(@StartTime)
DateTime(@EndTime)
TimePeriod(@TimeStep)
)Error message: The table-valued function definition is not supported.
1 vote -
Add support for unit conversion
Please add a "Canonical UOM Per UOM" or "UOM Per Canonical UOM" column (not necessarily with those exact names) to the UnitOfMeasure table. This column would contain the conversion factor needed to convert between the UOM and the canonical UOM, similar to the "Canonical" column in PI System Explorer when you are viewing a UOM class.
With this in place, a user can easily convert a value to any unit by first converting from the value's default UOM to the canonical UOM of the value's UOM class, and then convert from the canonical UOM to the desired UOM. This would…
1 vote
- Don't see your idea?