Forum Discussion
Table visual missing random values
- 2 years ago
Unfortunately adding the RELATED column didn't help either - it still pulled in a lot of nulls where there is definitely values.
But, I persevered and finally found a work around.
My labor table is not tied directly to the job detail table - there's a couple more layers in between. In a perfect world, this would be a single table and I would be able to create a hierarchy, but sadly the data source I have to work has it all divided into separate tables. So it goes job detail to department (as 1:*), then dept to task (also as 1:*), then task to labor (also as 1:*). Ultimately it still flows through the whole series of four tables as a continuous 1:* relationship.
But those couple extra layers seem to be the problem. I tried creating a duplicate of the top level job detail table and reduced it to just the key column and the couple extra columns I need, then created an active relationship directly to the labor table (with an inactive relationship to the original high level job detail table). Now when I pull in the required SERIAL column from the extra little job detail helper table, I don't get blanks anymore.
I guess you use a 'Many-to-many relationship'.
Please read a URL below.
I would recommend you to use ’One-to-many relationships'.
https://learn.microsoft.com/en-us/power-bi/guidance/relationships-many-to-many
It's already a 1:* relationship (1 job code to many labor entries)
- mickey642 years ago
Super User
How about adding a column to the table?
- CalanFCfx2 years agoFrequent Visitor
Unfortunately adding the RELATED column didn't help either - it still pulled in a lot of nulls where there is definitely values.
But, I persevered and finally found a work around.
My labor table is not tied directly to the job detail table - there's a couple more layers in between. In a perfect world, this would be a single table and I would be able to create a hierarchy, but sadly the data source I have to work has it all divided into separate tables. So it goes job detail to department (as 1:*), then dept to task (also as 1:*), then task to labor (also as 1:*). Ultimately it still flows through the whole series of four tables as a continuous 1:* relationship.
But those couple extra layers seem to be the problem. I tried creating a duplicate of the top level job detail table and reduced it to just the key column and the couple extra columns I need, then created an active relationship directly to the labor table (with an inactive relationship to the original high level job detail table). Now when I pull in the required SERIAL column from the extra little job detail helper table, I don't get blanks anymore.