Forum Discussion
Cluster Chart between two tables - displaying x axis values where only one table is populated
It came from the date table.
But you were on the right path with the cross-filter direction. For simplicity's sake, I didn't mention the multitude of other tables in this dataset. It was a relationship direction problem with a separate reference table that was messing things up.
For anyone that stumbles upon this troubleshooting their own concern: For some reason, I had 'accounting''s relationship to a separate 'job info' table (reference with information about projects) set as both ways cross filter, and my 'budget' table also has a relationship with that table due to common job numbers. So even though relationships were correct on the 'date' table, the cross-filter relationship on that separate reference table was allowing the 'accounting' table to filter the 'budget' table's date values for the visual. When I switched that to one direction relationship 'job info' (one) ----> 'accounting' (many), the visual was instantly fixed.
Thanks so much for the responses and getting me down the right track.
Community ChampionThe relationship between the accounting table and the date table, which crossfilter direction does it have?
/ J
single, date to accounting, one to many
- tex628
In your graph, the x-axis dimension "Week date", does it come from the accounting table or the reference date table?
/ JIt came from the date table.
But you were on the right path with the cross-filter direction. For simplicity's sake, I didn't mention the multitude of other tables in this dataset. It was a relationship direction problem with a separate reference table that was messing things up.
For anyone that stumbles upon this troubleshooting their own concern: For some reason, I had 'accounting''s relationship to a separate 'job info' table (reference with information about projects) set as both ways cross filter, and my 'budget' table also has a relationship with that table due to common job numbers. So even though relationships were correct on the 'date' table, the cross-filter relationship on that separate reference table was allowing the 'accounting' table to filter the 'budget' table's date values for the visual. When I switched that to one direction relationship 'job info' (one) ----> 'accounting' (many), the visual was instantly fixed.
Thanks so much for the responses and getting me down the right track.
- tex628
I'm happy to hear that you managed to solve it! Double sided relationships can cause quite alot of issues and It's not always so easy to grasp just how they affect the datamodel. On the other hand they can allow you to do certain things that simply are impossible with single sided. 🙂
Br,
J