Passing Parameters from PI Vision Display to AF Linked Tables: Troubleshooting Guide

Passing Parameters from PI Vision Display to AF Linked Tables: Troubleshooting Guide

In the world of operational data management, PI System by OSIsoft stands out as a robust solution for real-time data integration. As users build more complex applications and dashboards—such as those using PI Vision displays and Asset Framework (AF) linked tables—a common challenge surfaces: ensuring that parameters, such as time contexts, are accurately passed along these integrations.

Problem Outline

One particular issue that practitioners face is the failure of PI Vision display EndTime to be correctly passed into a linked table query defined in AF. Users have reported that while single timeseries attribute lookups work correctly in ProcessBook (PSE), attempts to incorporate these attributes within a PI Vision display result in the table displaying "No Data". During troubleshooting, it becomes apparent that the query’s EndTime parameter defaults to "Now", irrespective of the actual EndTime configured within the display.

Investigation and Solution Approaches

Common Approaches Tried

1. Parameter Substitutions: Attempts to substitute query parameters using strings like %UtcEndTime%, %EndTime%, %UtcTime%, and %Time% have been unfruitful.
2. Formula Attributes: Utilizing a formula attribute with the %time% placeholder has similarly shown limited success; although the attribute responds to the PI Vision's EndTime context within a value symbol, its efficacy as a parameter variable has not been manifested.

Insights and Next Steps

Upon deeply analyzing such cases, here's a structured approach that may yield better results:

1. Verify Configuration Settings: Double-check that the configuration syntax for parameter placeholders is accurate and conforms with the table lookup specifications. Misconfiguration is a frequent cause of such discrepancies.

2. Check PI Vision Configuration: Ensure that PI Vision is set to update display settings and recognize new parameter value changes. The default behavior might not automatically trigger a data query refresh upon parameter changes.

3. Leverage Alternative Attribute Data References: Consider creating an additional AF attribute with a date/time data type specifically intended to handle EndTime values, with precise reference to PI Vision updates.

4. Explore PI Vision Data Update Settings: Check the data update intervals and the mode of data fetching within PI Vision settings. It might be necessary to manipulate these settings to ensure that data is queried dynamically as per the defined context.

5. Consult OSIsoft Community and Support: Often, similar challenges are discussed in OSIsoft PI Square community forums. Engaging with the community or opening a support ticket might uncover undocumented nuances or product bugs.

6. Implement Workarounds: If a direct solution remains elusive, consider a workaround that pre-processes the EndTime externally and updates the linked table sequentially with exact timestamps before the query runs.

Conclusion

When dealing with sophisticated integrations like PI Vision with AF linked table queries, parameters such as EndTime passing require precise configuration and an understanding of dynamic context settings. While issues like these may be tricky to resolve, employing a methodical pursuit of solutions—including verifying settings, considering alternative attribute references, engaging with the community, and persistence—can bridge the gaps and enhance the reliability of your PI System applications.

Further Reading

Engage with the PI Square community for updated practices and discuss more nuanced use cases with fellow experienced users and OSIsoft engineers. Standardizing best practices can greatly aid in navigating similar future challenges.

Always keep your applications up to date and consult the latest OSIsoft documentation for guidance on handling newer software versions and features.