1 of 1 people found this helpful
PI Datasets in ProcessBook can't be easily shared across multiple ProcessBook displays. You can create a dataset in a ProcessBook (.PIW) file that can be accessed from all of the embedded displays, but if you are using stand-alone display (.PDI) files it's a different story. You can duplicate them into multiple independent displays, but then you run into versioning and change management challenges because the datasets are not centrally located.
I understand that your question is motivated by the issue you mentioned in the thread Does the PI Performance Equation (Calculated) Points/ Tags update and back fill in case of Data Latency? My recommendation would be to consider moving these Performance Equations into Asset Analytics rather than PI Calculation datasets. Asset Analytics should be able to handle buffering delays a bit better than PE's. Plus, the disadvantage of PI Calculation datasets is that the source data for the expressions needs to be retrieved from the archive every time a user accesses the dataset. This could lead to potential performance impacts on the data archive server for long query timeranges.