Ataytis Assurance
Troubleshooting
The messages the visual shows on the report, what causes each, and fixes for the problems most tables run into.
Messages on the report
| Message | Cause | Fix |
|---|---|---|
| Add your data fields, then select Edit on the visual to choose a diagram and customise its appearance and behaviour. | No columns are in the visual's field wells yet. | Drag your columns into Data fields, and numbers into Values. |
| Map Node type and Relationship type to draw this diagram. | The roles named in the message have no column mapped. The names depend on the diagram type. | Add a column for each, or open the editor and choose one for each role on the Data Mapping tab. |
| Complete the required data mappings. | A role the diagram type requires has no column mapped. | Select Edit on the visual, then map the required fields in Data Mapping. |
| No rows are available for this diagram. | Filters or slicers leave no rows, or no data is bound. | Review the report filters, or add rows to the bound data. |
| No valid nodes were generated. | No row produced a node, usually because Node ID is empty or mapped to the wrong column. | Review the Node ID values and mapping in the advanced editor. |
| The diagram layout is not available. | The layout could not be calculated. | Review the Validation tab in the advanced editor. |
| Checking the Power BI license entitlement. | The Power BI Service is confirming the viewer's licence. | Wait for the check to finish. If the visual is then blocked, the viewer has no licence. |
| Ataytis Assurance could not render this view. | An unexpected rendering error. | Refresh the report, or review the bound fields in the advanced editor. |
Common problems
| Symptom | Cause and fix |
|---|---|
| The Format pane has no settings | It only says Open Advanced edit mode to configure. The settings are in the editor: select the visual, open More options (…) and choose Edit. |
| Nodes draw but no connections | Connected node is not mapped. Map the column naming the other end of each connection, such as Parent ID, To state or Next state, to Connected node. |
| The diagram is upside down or starts at the wrong end | Connections are read the wrong way. On a bow-tie, every threat is reported as never reaching the top event. Change Connection column → Reads as on the Data Mapping tab. |
| A relationship references a node that is not present | The identifiers do not match. Where they differ only by spaces, the message quotes both values; trim the column in Power Query. |
| A column is bound but not used | It is in the wrong well. A text identifier in Values arrives as a measure; the message names the column and the well it needs. |
| Probabilities, rates or health values are too large | The column is being summed across rows. Set it to Don't summarize in the well, or set Summarization to Don't summarize on the column in Power BI. |
| A column shows in the Node Inspector but not in tooltips | Columns in Data fields that are not mapped to a role are shown in the Node Inspector only. Move the column to Values or Tooltips. |
| A bound column is missing from the Node Inspector | Its name matched a role, so it is used for structure. In a bow-tie edge list, names such as Control, Impact or Outcome bind to the register roles. Set that role to Not mapped on the Data Mapping tab. |
| A number column shows under Analysis instead of Metrics | Its name matched a value role. On a fault tree, a column called Threshold or Required Count binds to the voting threshold. Rename the column, or set that role to Not mapped on the Data Mapping tab. |
| A date on a node shows as a full timestamp | Label and Secondary label do not use the Power BI format. Show the date as a value annotation, or map a text column made with FORMAT. |
| Health is mapped to Status, or Health stays empty | A column named Health binds to Status when no column is named Status, State or Condition. Name the status column Status, or map both by hand. |
| A goal structure draws upside down, with the solutions at the top | The table names the element above each row. Change Connection column → Reads as on the Data Mapping tab. Few messages point to this; often only A solution cannot support a goal. |
| A column with a unit in its name does not bind | Names such as Failure Rate per Hour are not on the recognised list. Call the column Failure Rate, or map it by hand on the Data Mapping tab. A % sign is ignored, so Availability % binds. |
| Event tree outcomes show p instead of f, or no value | The initiating event has no Frequency, or a split is missing probabilities. Put Frequency on the initiating event's row and a probability on every branch of each split. The Validation tab says which is missing. |
| A Markov end state is missing, and a relationship references a node that is not present | The state has no row of its own. Add one row for it with Connected State ID left blank. |
| A Markov diagram starts from a failed state | Neither the states nor the transitions are typed, so the layout starts from the first State ID in sort order. Give the transitions a Transition Type of Failure or Repair. |
| Markov states report rows that disagree about Transition ID | A column named Transition ID is not recognised. Name it Relationship ID, or map it to Transition ID on the Data Mapping tab. |
| Markov transition probabilities are drawn under the states | A column called Probability binds to State probability. Name the column Transition Rate, or map it to Transition rate on the Data Mapping tab. |
| Node types are reported as not recognised | The wording is not on the recognised list. Map each value under Node type values on the Data Mapping tab. |
| The wrong diagram opens | The table holds several Diagram IDs. Choose one under Diagram → Show on the Data Mapping tab. |
| A bow-tie register reports several top events | The register holds more than one bow-tie. Add a Diagram ID column so each is its own diagram. |
| Readers in the Power BI Service see no diagram | They have no licence for the visual. Power BI shows its licence notification in place of the diagram. |
Reporting a problem
Include the diagram type, the messages listed on the Validation tab, and a few rows of the table with its column names.