Dynamic Query Tool v2

13 min

General Information

This is released as a beta initially, and you will have the option to move between the Dynamic Query Tool (DQT) v2 and DQT v1 using a DUP. You will need to upload the Meta Model EUP and v2 DUP to use this version (as of 19th February 2025). Get the EUP/DUP files from the release notes page.

To upload the EUP

  • You will need to perform these steps before applying the DUPs.
  • Go to Configure > System Administration, select Apply EUP
  • We recommend following the snapshot link and performing one before applying the EUP
  • Once you have taken a snapshot, return to the Apply EUP screen.
  • Choose File, select the EUP file, then Apply Updates.

To Upload the DUP

  • You will need to do this for each repository you want the DQT v2 to be in. Select the Import tab, then Data Import.
  • We recommend performing a snapshot for each repository.
  • Return to the Data Import
  • Choose File, select the DUP file, then Apply Updates.
  • Publish the changes to the viewer so that the updated DQT appears in your Editor List.

To return to the DQT v1, download the DUP from the release notes. Repeat the data upload steps as above, using this file instead of the DQT v2. You can switch between either version of the DQT using these two DUPs, depending on the version you want to use.

Dynamic Query Tool v2

This is an updated and enhanced version of the Dynamic Query Tool, with more advanced querying and more tools to assist when making queries. Users now have the option to save as queries or catalogues. When selecting the result fields, there is the ability to perform advanced slot/column selection, navigating to a specific value. Overall, v2 is a much-improved version of the DQT, with much deeper customisation of conditions for more specific results.

The latest version also gives you the ability to import/export queries, giving you the option to copy queries between repositories.

Selecting the Class

This is performed in the same way as before. Just select the main class you want to perform the query on.

Dqt Class Selected

Result Fields

There are now two options, with one the same as before, and a more advanced results field/column selection.

Dqt Initial Screen

For simple selection: The Select Result Fields button lets you choose the fields that you want to output once the query is complete. These will appear in the results table under the Query section after you run the query.

DQT simple Select Fields

 

For advanced selection: after selecting the Result Fields, click Advanced Slot/Column Selection. After this, there will be additional options for the column results, fixed, sort, and column width. You can also remove columns using the delete button. The Fixed option defines which column is scrolled from, e.g. if the second column was selected to be fixed, the first two columns will not slide in the query result graph. The Sort button defines what column the results table will initially focus on, but this can be changed by selecting the desired column.

Dqt Advanced Columns

Drag slots to be in a different position using the three lines on the left of the table.

Navigate button

Allows you to navigate to a value. E.g. if you selected stakeholders to appear in the results field, it displays not only the actor to role relation, but the actors playing the roles. You will need to select the green add button or when Close Navigation/Done is selected the add values will not appear as part of the query.

Dqt Navigate Columns

After selecting the slot, select the value type (class)

Dqt Navigate Columns 2

Repeat button

An example might be planned changes, in relation to Projects. This means for every planned change, all the result field columns will be repeated, and columns can be split out into the instance that is being changed, and the change being made. A column could be added for the impacted element, and the change action.

Here you can also change the Field Label.

Dqt Repeat Values

 

Run the query. Select Run Query to perform the query for the selected slots. Instances are repeated so that impacted elements/change action are in separate columns for the same project.

Dqt Repeated Instances

Advanced Filters (Conditions)

Use these after you have run a query. Continuing the Project Lifecycle Status example, you can add a condition that only shows lifecycle statuses that are in execution. Add as many of these as you need to.

Dqt Add Conditions To Table

You can also add a secondary condition to a single condition, click the ‘And’ button to change it to ‘Or’ so that a single condition can filter more than one instance.

Dqt And Or Conditions

Within the additional condition, there is the option to add further filtering conditions. Add another condition, so that there are at least three. Then select the arrow on the right of the second condition. You can now add and ‘And’ condition within the ‘Or’ condition already created.

Dqt Additional And Or conditions

Advanced Queries

Select a class. Add a search condition to the class to define where the query will be performed.

Dqt Add Query Conditions

Certain conditions will prompt a class within the condition, for example Strategic Plans Supported will give the option to filter by Enterprise Strategic Plan, Business Strategic Plan, etc.

Dqt Select Class Within Class

Within the strategic plan classes in the example, you can then select a specific plan from that class.

Dqt Select Slot In Class

You can now choose between adding ‘And’ or ‘Or’ conditions, adding as many of those as are required. So, in this example, you can add more strategic plans, even from different classes, to appear in the query table.

Dqt Advanced Conditions

You can also add conditions using dates. If the condition was a project start date, once you have set the conditions, there is the ability to filter by start date, using a date picker in the class/instance selection. This will only appear for certain classes.

Dqt Date Picker

Saving Queries and Catalogues

You can save queries and catalogues after the query has been performed.

Dqt Initial Screen

Saving a query creates an instance of a new type of class (found in Capture screen; EA Class > EA Support > Utilities > SYS Utilities > Query) and is performed in the same way as before. Select ‘Save As…’, then Query, give it a name, label, and description. Then select Save.

Dqt Save As Query

Saving a catalogue also creates an instance of a different type of class (found in Capture screen; You will need to enable this class in the Class Editor before saving catalogues. In the backend repository select, Configure > Class Editor, then in the class tree, EA Class > EA Support > Essential Viewer > Report > Editor > Catalogue. Select the LAYOUT tab and select the Enabled box, then it will appear in your Class Tree. This provides the option to add additional details about your query. performed by selecting the save as button, then selecting the Catalogue option.

Dqt Save As Catalogue

To load saved queries or catalogues, select Open Library. Then Query or Catalogue. You will only have the option to load queries or catalogues that are not already open.

Dqt Open Query or catalogue

Once you have saved a query/catalogue, you can still make changes to it. If you want to update the same query/catalogue, select the blue Save button. If you want to create a new query/catalogue, select Save As and save as before.

Dqt blue Save Pulse

Export

Here you can export your queries and catalogues. This will download a copy of the query and allow you use those exact query terms in other repositories, without having to add all the conditions again. This also creates a copy of the query that can be stored locally.

Import

Use this to copy your exported queries/catalogues from different repositories.

Updated 3 March 2025

    Contact Us