Forum Discussion
Calulated column question
- 9 years ago
kudos to CS for putting in so much time. I am following this post because I come from the SQL world and it is a classic Unmatch query; and so I'm interested to see how it is implemented in PBI.
In SQL one would have a Parts table (all Parts & Part Type only, no repeats)
Then you would make the 1st unmatched record set which is those sales records where the 2 types do not match.
That would then be made distinct of Part field only so there are no repeats: DistinctUnMatch1
Then you would left outer join Parts to DistinctUnMatch1.
That returns all Parts records but in the UnMatch1 Parts field there are nulls where nothing can match.
This record set is UnMatch2. ... you apply criteria so it only returns the Nulls records- which by definition is the record set that are the Parts with only matched Customer & Part Type.
I may be out of date on PBI capability but I don't think one can define a left outer join - so I presume that is why one is working with yes/no comparisons instead and then a filter.
Hi robofski,
Anonymous has done some great work, but I often suggest completing this type of complicated output using the Query Editor.
The query editor is very robust and can create an additional column a lot easier and in a step by step process, which makes it easier to work through.
As well as if you create it using the Query Editor, it will get better compression into your data model.
Hi GilbertQ
I agree it could be better with Query Editor and can walk through step by step.
Next time will look at this option, instead of measures.
Thanks for the valuable feedback.
Cheers
CheenuSing