Forum Discussion
Data Modeling: Connecting to a Dimension Table Twice
sem1 you will be able to slice on original port (assuming it is active relationship) but if you also want to slice on destination port, in that case recommendation would be to have two table one for origin and one for destination and then set relatnship with respective table with shipment table.
Above will be more flexibile and will meet most/all the requirements.
sem1 the best option is option 4, set relationship between location table and shipment table on both origin and destination port id. One relation will be active and other inactive coz there can be only one active relationship between tables. In mesure use USERELATIONSHIP function for inactive relationship and you will able to achieve desired results.
Would that enable me to use both dimensions in a chart? Or would I only be able to use one.
I.e.:
| OriginPort | DestinationPort | Shipments |
| Shanghai | Rotterdam | 10 |
| Antwerp | Shanghai | 5 |
| Rotterdam | Antwerp | 13 |
I'd also like to be able to use slicers/filters to filter them. So for example if I look at the origin of Shanghai, I want to see the destinations I'm shipping to.
sem1 you will be able to slice on original port (assuming it is active relationship) but if you also want to slice on destination port, in that case recommendation would be to have two table one for origin and one for destination and then set relatnship with respective table with shipment table.
Above will be more flexibile and will meet most/all the requirements.