Create Extension Query (Classic)

This topic describes how to create an Extension query.

Before you begin

Log in to Operations Hub.

About this task

Extension type queries work with multiple data sources.

Procedure

  1. In classic Operations Hub navigation menu, select QUERIES.
    The QUERIES workspace appears.
  2. Select Add new query.
    The New Query window appears.
  3. Provide these details:
    Field Name Description
    Name Enter a name for the new extension query. The name must contain at least one uppercase or lowercase letter.
    Type Select Extension.

    Additional options for creating the extension query appear.

    Description Briefly describe the purpose of the query.
    Method Select the type of extension query you want to create from these options:
    • Read
    • OPC UA Write
    • Historian Add Comment

    The sections Query Parameters and Output Data appear based on the method selected for the query.

  4. Specify Query Parameters.
    1. Choose from:
      • Fixed Value: If this option is selected, the provided value is considered as a fixed value for the field. Fixed value fields are not shown in the application page builder.
      • Input Field: If this option is selected, the provided value appears as a default value for the field in the page builder. Any value provided before executing the query overrides the default value.
    2. Select next to the parameters you do not want to include in your query.
      To retrieve deleted query parameters and output data, select +Add All Query Params and +Add All Outputs respectively.
  5. Under the Output Data section, you can include one or more output data fields to your extension query.
    Following output fields are available to use:
    Output Data Field Description
    Timestamp This field represents the timestamp associated with each data point.
    Name This field represents the tag name you want to query in the database.
    Value This field represents the actual data value associated with the specified tag at a given timestamp.
    Quality This field represents the quality of the data at a specific timestamp.
    Data Attributes This field represents data attributes associated with the data point.

    Historian is now enhanced to store up to 128-bit quality types, which are stored in data attributes. These attributes are extended qualities that you can store more than the regular qualities and sub qualities such as good and bad. In addition to regular qualities, the HAB collector collects extended qualities such as replaced, suspect, garbage, old, and so on. You can use these attributes using REST APIs as well as Configuration Hub.

    Select next to the output data field you do not want to include in your query.

  6. Save the extension query.

Results

The extension query is created. The newly created query appears in the application page builder under PAGE DATA > Query > Entities.

What to do next

Go to the application page builder to apply and execute the query.