Forum Discussion
Helper IIIRelationships in data model does not work - breaks table visual
Hi mtomova ,
I wanted to check if you have had an opportunity to try the bridge table approach.
Community ChampionBest practice: Keep star schema → use property_table as dimension, and show measures/installation separately.
If you need both in one row → create a bridge table (property_id, measure_id, task_id).
If you just need to show related fields → use DAX (LOOKUPVALUE / TREATAS).
Helper IIIHi, thank you, I thought that the 'bridge' table is the proper approach if we want to combine the data.
I have never done it before, but will give it a try and see how to relate the tables.
As for the LOOKUPVALUE, wouldn;t that throw an error, because I will return multiple match per property_id?
Hi mtomova ,
I wanted to check if you have had an opportunity to try the bridge table approach.