Forum Discussion
Overlapping data slicer
- 5 years ago
Robert93 Disconnected tables are just tables with no relationship between them. I have mocked up a solution in attached PBIX below sig. You want Page 8, Table (8) and Table (8a). Basically, split your wire range out into a min and max and then implemented a Complex Selector that you use in your Filters pane.
Measure 8 = VAR __Currentkm = MAX('Table (8)'[km location]) VAR __Minkm = MIN('Table (8a)'[km locations min]) VAR __Maxkm = MAX('Table (8a)'[km locations max]) RETURN IF(__Currentkm>=__Minkm && __Currentkm <= __Maxkm,1,0)
Hi Greg_Deckler,
thanks for the quick reply.
Sample data would be something like the following,
| km location | thickness (cm) |
| 0 | 12 |
| 1 | 10 |
| 2 | 11 |
| 3 | 12 |
| 4 | 13 |
| 5 | 15 |
| 6 | 16 |
| 7 | 12 |
| 8 | 10 |
| 9 | 15 |
| 10 | 9 |
And from the knowledge of the sections, I know that,
| Wire | km locations |
| A | 1 to 3 |
| B | 2 to 6 |
| C | 5 to 8 |
| D | 7 to 10 |
The overlapping sections of wire are where they join to one another (one gradually decreases while the other gradually increases). This is sample data where the overlaps are 1 km. Really these are smaller values but the idea is the same.
I have the first set of data plotted out over a line visual, I would like to have a slicer that has options Wire A, Wire B, Wire C, and Wire D. When selected, the km axis just shows data in that range.
More than happy to learn the ways to make this happen. I haven't heard of either disconnected tables or binning.
Any help would be greatly appreciated.
Robert93 Disconnected tables are just tables with no relationship between them. I have mocked up a solution in attached PBIX below sig. You want Page 8, Table (8) and Table (8a). Basically, split your wire range out into a min and max and then implemented a Complex Selector that you use in your Filters pane.
Measure 8 =
VAR __Currentkm = MAX('Table (8)'[km location])
VAR __Minkm = MIN('Table (8a)'[km locations min])
VAR __Maxkm = MAX('Table (8a)'[km locations max])
RETURN
IF(__Currentkm>=__Minkm && __Currentkm <= __Maxkm,1,0)- Robert935 years agoRegular Visitor