AdminChris Manhard
(Software Engineer, OSIsoft)
My feedback
-
4 votes
-
1 vote
The OR clause is planned for AF 2018 SP2 and will be available in PI Builder, although it requires typing of the OR clause directly in the search box - for example: "Template:T1 OR Template:T2".
In AF 2017 and later, you can also include multiple templates IF you can identify them by name with wild card using the TemplateName filter. For example "TemplateName:T*". Note that this clause must be typed into the to search box - there is not an independent control on the search form.
-
2 votes
Can you clarify? In PI System Explorer, you can specifically choose which elements you wish to export by multi-selecting them in either the "Child Elements" tab - or - doing a search and multi-selecting them in the results grid. Right click on one of the selected elements, and export.
You cannot, however, choose to NOT export the child elements of any particular element you have selected in PSE. So, for example, it would not be possible to export a parent element and only some of it's children.
Within the AF SDK, this is possible by using the PIExportMode.NoReferences flag and passing a specific list of elements (the NoReferences would also cause no Analyses, Notifications or associated Templates to be exported)
-
9 votes
For the spans implementation, let’s consider implications on PI, OCS and EDS. E.g. how does the data source represent spans and/or how does the OMF application recognize these spans? Who / what uses the span data? How does the thing using the span data represent a span and associated data? Do we have scenarios with non-time based spans for OCS and EDS?
AdminChris Manhard
(Software Engineer, OSIsoft)
supported this idea
·
-
1 vote
This has worked for some time in PSE. Is there a specific use that I am not understanding?
-
3 votes
You can get the top level root via the %\Element% substitution parameter. Getting other levels is not currently possible without additional string builder's which can copy down the attribute as suggested
-
3 votes
Can you explain why you need access to this dialog for the built-in data references? That is, why is this dialog more useful than the built-in dialogs?
-
12 votes
Just making sure you are aware you can add these columns via the settings drop-down in the grid view of af elements, eventframes, and most other "top-level" objects . Once you add the columns, the setting will be remembered. They are not currently shown by default, however.
-
5 votes
The step attribute indicates a basic behavior of the data, and controls more than the trend - but behavior in interpolation. If the change is only for the behavior of a trend - perhaps it would be better to override the behavior in a trend setting. Can you explain a bit more the use case?
The step attribute indicates a basic behavior of the data, and controls more than the trend - but behavior in interpolation. If the change is only for the behavior of a trend - perhaps it would be better to override the behavior in a trend setting. Can you explain a bit more the use case?
-
2 votes
I can see that the "Clear to Empty Cell Boundary" option is not always being honored in the new import case, only during "Retrieve". We will try to address that in a future release.
I can see that the "Clear to Empty Cell Boundary" option is not always being honored in the new import case, only during "Retrieve". We will try to address that in a future release.
Under the Settings menu item, for the Retrieve tab, there is a setting to control the addition of the two row/column border. If you change the setting to "Clear to Empty Cell boundary, and then also leave the header row blank past the last PI Builder utilized column, this should achieve what you want.
-
15 votes
Is the request for this specific to a client application, such as PI Vision?
-
11 votes
Is this specific to PI System Explorer, PI Builder, or PI Vision? PI Builder does have this option. PI System Explorer does not.
-
4 votesAdminChris Manhard
(Software Engineer, OSIsoft)
supported this idea
·
-
6 votes
In response to Zev Arnold, "Nope! I was wrong. I fixed my issue, b..."
There are many things that make an on-demand rollup taxing on the system - more so than might be apparent. General expectations for time-series based attributes is the ability to notify on change, summarize, trend, interpolate, calculate previous values, etc. Meeting those requirements and dealing with a potentially dynamically changing and potentially quite large set of input attributes - including nested rollups - does not make sense when we have the PI Data archive available to store those results. Is there a particular reason, other than cost of a tag, that you are avoiding tag creation? -
7 votes
The upcoming PI Builder 2017 release will support PI and AF Identities and Mappings.
-
1 vote
Can you be more specific? AF has been making improvements to the security setting dialog each release of AF Client. AF 2.9 will also have the ability to edit identities and mappings of PI Data Archive and AF Server within PI Builder, allowing users to more easily share identities and mappings between servers.
A future enhancement request we are aware of is to allow users to see the effective permission of a particular user or identity within PSE or eventual web-based configuration tool.
-
12 votes
It will not be possible to dis-allow read permission on templates.
However, by default, Event Frames get their read permission from the ReadData permission of the template. Would it be adequate to remove the templates for which the user does not have ReadData permision from the search list in Datalink (and PSE, Coresight, etc?).
-
45 votes
Is there an expectation that the description reflects the substitution pattern automatically after initial creation?
For example, Name substitution patterns defined in the template are applied on initial creation, otherwise, must be manually re-applied.
Also, for this to work at the attribute level, AF would have to enable attribute override of description - which is currently not possible (although often requested and on our radar). There are performance and storage implications for this feature that have to be considered. We are cautious when a simple feature such as this can lead to surprising and drastic changes in performance and scale.
Dynamic re-evaluation of description substitution is difficult because it impacts features like search which work best with a fixed index-able value.
If there were multiple UOMs abbreviations, applications may accept them, but they would all be displayed using the same standard abbreviation. Roger, your use case of using in different locales would not apply, unless we also added locale information to each abbreviation. The complexity there is likely unwarranted.