Simon J. Dyson
My feedback
-
1 vote
An error occurred while saving the comment -
2 votesSimon J. Dyson
shared this idea
·
-
7 votesSimon J. Dyson
supported this idea
·
An error occurred while saving the comment Simon J. Dyson
commented
BadVal should return TRUE if the input argument has a bad quality. So for a PIPoint DR this would be when the value is a digital state (for numeric), or digital state outside the digitalstate set, including system states. For formulas, I would expect that things such as "divide by zero", "all events filtered", "no events", "No data", "unknown attribute" etc etc would be treated as bad values. In the same way as the IFERROR function works in Excel.
BadVal should do what it says it should, i.e. detect when the argument is bad. This saves a lot of defensive logic to be added to the formulas when it should be a standard function.
-
22 votesSimon J. Dyson
supported this idea
·
An error occurred while saving the comment Simon J. Dyson
commented
IFERROR equivalent functionality would make validation and formula simpler. Or better still BadVal should work as you would expect. E.g. why doesnt a divide by zero error get picked up by BadVal?
-
68 votes
At this time, this item is not currently scheduled for a release of PI Vision. If this changes, this item will be updated to reflect the current status.
-
26 votes
An error occurred while saving the comment Simon J. Dyson
commented
I would also like to have the SUMPRODUCT functionality within PI AF.
-
8 votesSimon J. Dyson
shared this idea
·
-
100 votesEVALUATING · 12 comments · Customer Portal & PI Square » Customer Portal Overall · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Simon J. Dyson
commented
Agree.It is not easy to see what are the current versions of products as the FEED is pretty useless. I end up having to go into each product and the downloads section, but even here the correct versions are not shown. For example AF client MUI latest version is SP2, but the version name shown is 2018 SP2A for everything. Which means you don’t know what has actually changed.
Simon J. Dyson
supported this idea
·
-
32 votesSimon J. Dyson
supported this idea
·
Example
{
"AM/HV270618" : {
"Temperature" : "OK",
"Pressure" : "IMPAIRED",
"Voltage" : "IMPAIRED"
}
}
Where the first name is the name of the asset to which the following attribute values are to be assigned in the target system. PI Notifications doesnt allow the value of the "name" to be assigned through an AF attribute reference in a template or substitution parameter such as %Element%.
If the above is valid JSON syntax, then PI should also support this format.