do you have any suggestion on how to structure the data to properly work on QS?
Since we cannot use relationship at the moment, see Multiple Datasets to be connected like "relationship" than "join" I would need a valid workaround.
I will explain the use case with this image:
Can you think on a more efficient workaround? to avoid using calculated fields in this way.
The higher hierarchy levels that you want to filter on will need to be in the dataset that drives the visual. Consider introducing a hierarchy relationship table with a flattened structure like the sample given below. In base tables, use hierarchy level key and hierarchy level columns and then join with hierarchy relationship table on those columns while pulling data into datasets (You can also do a custom sql mapping the specific level key from base table and hard coding the level against the hierarchy relationship table). This will help you get all the higher hierarchy levels into datasets in a scalable way.
(There is the alternate option to use cascaded filter controls. But that can be used only if you always make selections all the way to lowest level of the hierarchy. I don’t think that will work for your use case. Just mentioning this option as well for completeness)
Hi Arun, thanks. Your methodology is what I’ve applied so far, the problem is that I have much more levels and this is not scalable
Hi Andrea. I’ll communicate this feature request to the correct team