Table of Contents

Altus Matrix

Configuration

Example for Issues Matrix on Project

This image displays the Altus Matrix configured for Issues with numbers on axis

This image displays the Altus Matrix configured for Issues with labels on axis

Entity Form Configuration
  1. You will need to either create/have a customisation solution. In this solution you will need to add the desired Entity which contains the desired form you wish to customise.
    • In our case that is a solution called Customisation with the existing entity, Project with the form Tracking.
  2. If you are looking to use the filtering component as we are of the subgrid attached we need to get the Name under "Specify a unique name" in the corresponding subgrid. This is "Subgrid_Issues" in this case. Take note of this for the configuration of the "Altus Matrix".
  3. Define the label of the matrix displayed by defining Label on this page under the Name section.
  4. Configure the entity that is mapped by specifying the Data Source. In this case its for Issues. List or Chart properties - Display panel configuration
  5. Configuration of the Altus Matrix Control. Add the control Altus Matrix under controls and dont forget to change that it should be used for all forms of presentation (Web, Phone and Tablet).
    • Entity field bindings is going to be automatically mapped from your selection in the Display component where a mapping is created for the issue entity.
    • JSON config setting this is the name you choose for the configuration setting you will define later on. In our case we have SenseiProjectIssuesConfiguration_IQA keep this somewhere for later.
    • Subgrid Name shall be the Name from part 2 above.
    • Parent Relationship Field this is in this case the sensei_project as that is the parent used in part 1. This needs to be lowercase or the grid wont render. If you have created a custom entity you will need to lookup the corresponding Parent Relationship Field ie cr78f_project. Add the Altus Matrix as a control and configuration example for issues
Configuration Setting Setup
  1. An Admin will need to open two browsers to the configuration settings page. We are going to go to the inactive setting on one page and look for in our case SenseiProjectRiskConfiguration_IQA. SenseiProjectRiskConfiguration_IQA configuration setting example

  2. On the second browser navigate to the configuration settings page. Click add New configuration setting. Label it with an appropriate Category, Display Name, Description. Set the Name equal to the JSON config setting Name from earlier, ie. SenseiProjectIssuesConfiguration_IQA

    NOTE: if you would like the X and/or Y Axis Labels to display the choice set labels you will need to set the value in the X Axis Label Max Length and Y Axis Label Max Length fields so that they equal >0. If they are set to 0 they will only display numbers.

  3. As a template we are now going to copy the JSON Schema and UI_Schema from first page by clicking the gear in the bottom right hand corner. Copy the JSON Schema to the second page in the Json Schema section, then also Copy the UI Schema from first page to the second page. SenseiProjectRiskConfiguration_IQA copy JSON schema and UI schema

Customisation via Configuration Setting

Below is an example of the configuration of issues matrix further details will be explained below.

SenseiProjectIssuesConfiguration_IQA configuration example

Note

For more information on how to configure the Matrix click here.

Customisation Steps
  1. Choose your row and column you wish to display.

    • You will need to get the internal name for the desired entity. ie Issues has Priority (sensei_priority) and Category (sensei_category). These need to be lowercase for it to work.
    • Navigate to make.powerapps.com then select the environment that contains Altus select the Tables in left hand column. Once you select it select all then in the right hand corner search for Issue in this case. Then under schema click columns. Then you are going to be looking for a datatype of Choice. Then you can lookup Name column as shown below. Displays make.powerapps.com Entity Table for Issues to inspecting 'Name' component of a Choice
  2. We then can adjust the values after saving the configuration for each of the axis. This involves changing the Axis Label

    • Noting that if your field ends with index you can leave 'index' off and update the field ie in Risk matrix. with index otherwise it should be populated with dataset. In this example sensei_priority and sensei_category are selected with the corresponding dataset tag.