Data notes
What Ataytis BOM reports about a table, where the notes appear, what the visual does in each case, and how to fix the data.
Data notes say what the visual found in the table, what it did about it and, where there is one, what to change. None of them stops the BOM drawing.
Where they appear
- In the editor header, as a count: for example 12 items · no problems, or 12 items · 3 notes. Selecting it opens the Data tab.
- On the editor's Data tab, under Data notes, each with up to five examples from your data.
- On the report, from a Data notes button on the toolbar. It is off by default; turn it on under General → Toolbar → Data notes.
The notes
Each note starts with how many times it was found in your data. They are shown here as they read when that number is 2 or more.
| Note | What the visual does | What to change |
|---|---|---|
| 2 circular references found | A component eventually contains its own parent. The branch is shown once and marked where it loops. | Correct the relationship in the source data. |
| 2 loops not reached from any top-level product | Every route into these items passes through a circular reference, so they are shown from the loop itself. | Correct the relationships that form the loop. |
| 2 rows list an item as its own child | The rows are skipped. | Remove or correct them. |
| 2 quantities could not be read as numbers | The quantities are treated as unknown, so extended quantities through those lines are left blank. They are also counted in the next note. | Correct the value, or make the column numeric. |
| 2 relationships have no quantity | Extended quantities beneath them are left blank. A quantity that could not be read counts here too, because it gives no usable number. | Fill in the quantity, or correct the one that could not be read. |
| 2 rows have a parent but no child | The rows add nothing. The parent still appears as an item. | Fill in the child, or remove the row. |
| 2 part numbers differ from another only by case or spacing | They are kept as separate items. | Make the part numbers identical in Power Query if they are the same part. |
| 2 relationships appear on more than one row | The quantities are added together, or the first row is used, as Repeated parent and child says. | Nothing, if that is right. A Details column such as a position, version or date usually explains the repeats. |
| 2 blank rows skipped | Rows with neither a parent nor a child are ignored. | Nothing. |
| Power BI stopped sending rows at 30,000 | The BOM shown may be incomplete. | Filter the report to fewer products. |
The numbers in the notes come from your data. The last one is also shown above the BOM, even with the Data notes button turned off, because an incomplete table gives a wrong BOM.
A table that raises most of them
| Parent | Child | Quantity |
|---|---|---|
| KIT-A | BRACKET | 2 |
| KIT-A | BRACKET | 2 |
| KIT-A | KIT-A | 1 |
| KIT-A | SCREW | four |
| KIT-A | Screw | 1 |
| KIT-A | WASHER | |
| KIT-A | SUB-1 | 1 |
| SUB-1 | SUB-2 | 1 |
| SUB-2 | SUB-1 | 1 |
- A circular reference: SUB-1 → SUB-2 → SUB-1.
- A row listing an item as its own child: KIT-A.
- A quantity that could not be read as a number: KIT-A → SCREW, whose quantity is four.
- Two part numbers that differ only by case: "SCREW" and "Screw".
- Two relationships with no usable quantity: KIT-A → WASHER, which is blank, and KIT-A → SCREW again, because four could not be read.
- A relationship on more than one row: KIT-A → BRACKET, drawn once with a quantity of 4.
The row limit
Opening every branch of a large BOM with many shared sub-assemblies can run to millions of positions. When the positions on show reach the row limit, the bar above the BOM reads, for example, Showing the first 200,000 rows. Collapse branches or choose a product to see the rest. Raise the limit, up to 1,000,000, under General → Opening → Row limit.