The Report Designer/Data Source page allows users to.

• view, search and select data sources to be used in a report.

• set up and validate relationships between data sources in a report.

Open

Figure 1.1

• STEP 1: Click the New Report (+) icon on the left-hand menu and select New Report. You will be directed to the Data Source page.

• STEP 2: Browse the visible tables, views, or stored procedures provided by Riskonnect in the Middle Panel.

• STEP 3: Collapse or expand categories by clicking the category name to manage the view efficiently.

Open

Figure 2.1

Open

Figure 2.2

• STEP 4: Use the Search box at the top to find specific data sources by typing a partial name and clicking the search icon. Matching data sources or fields will be displayed.

Open

Figure 2.3

• STEP 1: Click the + icon next to a data source to select it. Selected data sources appear in the top section.

• STEP 2: Existing relationships between selected data sources are automatically added to the Relationship list in the Content Panel.

Open

Figure 3.1

• STEP 3: To remove a data source, click the bin icon next to the data source under “Selected Data Sources.” Confirm removal; relationships linked to deleted data sources will also be removed.

• STEP 1: Tick the Distinct checkbox at the top of the Middle Panel to return only unique values in the report.

• STEP 2: Leave it unticked to allow duplicate values in the results.

Configure the amount of data shown in the preview panel by selecting from the Preview Records dropdown at the top.

• STEP 1: Click the Save button at the top to open the Save pop-up.

• STEP 2: If the report is already saved, choose Save As to create a new report.

Open

Figure 6.1

• STEP 3: Enter a name for the report in the Report Name box.

• STEP 4: Select Save as Template (or Save as Report after adding at least one field).

Open

Figure 6.2

• STEP 5: Choose a Category and optionally a Sub-Category. You can create a new category or sub-category by typing the name and pressing Enter.

• STEP 6: Click OK to save the report.

Open

Figure 6.3

• STEP 1: Select multiple data sources to define relationships between them.

For example, you need to create a join manually in a case where you want to get the KPIs which are linked to Goals - this means that the Planning_KPILinks_STND must be joined with Planning_PlanningHierarchy_STND. This is usually not setup as a default because a KPI can link to Goal, Outcome or Strategy levels. When you wish to retrieve the KPIs linked to Goals only, you can build the following join relationship manually.

[KPILinks_STND].[GOALID] = [Planning_PlanningHierarchy_STND].[GOALID].

• STEP 2: Click Add Relationship to insert a new row in the Relationship list.

• STEP 3: Select values in the following order:

  • Join Type (e.g., Left)

  • Category, Data Object, Join Field

  • Category, Foreign Data Object, Field

Select values in Category, Data Object, Join Field, then Category, Foreign Data Object and Field in left-to-right sequence for data to populate correctly.

Select data so that the row reads: | Planning | KPILinks_STND | GOALID | = | Planning | Planning_PlanningHierarchy_STND | GOALID |

Open

Figure 7.1

• STEP 4: Click Validate Syntax to confirm the relationship.

Open

Figure 7.2

• STEP 5: Copy existing relationships using the Copy icon for faster setup.

• STEP 6: Remove unnecessary relationships using the Remove (X) icon.

• STEP 1: After creating a basic join, click Add Key Join to insert a blank row for additional columns.

• STEP 2: Select values in the same left-to-right sequence as normal relationships.

• STEP 3: Click Validate Syntax to confirm.

Open

Figure 8.1

• STEP 1: Assign a Join Alias when joining the same table multiple times to differentiate data objects.

• STEP 2: Select Join Type, Category, Data Object, Join Field, Field Comparison, Foreign Category, Foreign Data Object, and Foreign Field.

• STEP 3: Use meaningful aliases (e.g., Parent vs Child Project) to avoid confusion in subsequent join clauses.

For example, to get data of Parent Projects and Child Projects, the Project_ProjectDetails_STND dataset needs to be joined with itself:

Since the Project_ProjectDetails_STND datset is used twice it should be given a meaningful alias as shown - this allows you to differentiate between say the Project Owner of a Parent Project vs the Project Owner of a Child Project.

Open