About custom views
- Last UpdatedApr 08, 2025
- 3 minute read
Custom views enable you to choose data sets from different modules and sources, and create a compiled view of this data. Each of the AVEVA™ Production Management modules has a distinct view of data, and their own client-side presentation of that data. With custom views, you can analyze data across module boundaries.
Custom views also give users the ability to see data from different modules combined. This expands the viewable data beyond only that captured by reporting points. The merge and aggregation of data from many different sources provides a highly-customized view of data.
Like standard views in SQL Server databases, custom views in AVEVA™ Production Management consist of at least one source table. In AVEVA™ Production Management, this table is referred to as the primary table. The primary table can be sourced from any reporting point, or an Applications folder, as long as it contains reporting points.
If the view is to contain data from more than one data source, then these extra tables are referred to as secondary tables. It is possible to have any number of secondary tables. Secondary tables require a joined field with the primary table.
Benefits of custom views
Some benefits of custom views:
-
You can combine data from different modules.
-
You can also combine OLE-DB data from the secondary table.
-
You are not restricted to data captured by reporting points.
-
The merge and aggregation of data from different sources provides a highly-customized view of data.
Examples of custom views
Here are some examples of custom views you might create.
-
Data that is grouped and joined by shift.
-
Sum of production outputs, targets, and variances (Production).
-
Sum of production scraps (Production).
-
Sum of downtime durations (Downtime).
-
Count of work order requests (Maintenance).
-
Average oven temperature (Process Quality).
-
Filtered to show only production data that is confirmed.
-
Filtered to show only downtime data that is closed.
Join types for custom views
When the join type is Inner, all data from the Primary table is included in the custom view, and only data from the Secondary table that matches on join fields. When the join type is Outer, all data in both tables is present in the custom view. Also, when the join type is Outer, you can group on fields that originate from the Secondary table, in addition to fields from the Primary table. Use the JoinType property on the Secondary table to specify the join method between primary and secondary tables.
-
Inner - You can group on fields that originate from the Primary table.
-
Outer - You can group on fields that originate from the Primary table and the Secondary table.
For more information, see Create a join field.
Use evaluated fields in custom views
Some of the fields displayed in the custom view may be derived from calculations that are performed on the contents of other fields. For more information, see Select evaluated fields to use in custom views.