Forum Discussion
Combining Columns in Different Tables
Hi RichardLinderma ,
Thank you saritasw and Ritaf1983 for the quick response!
Could you please confirm if the issue has been resolved on your end? If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.
Thank you for your understanding and assistance.
Hi RichardLinderma
The solution depends on the model and the types of relationships—or even whether relationships exist at all—between the tables.
Therefore, to provide help, we need to see what you’re working with.
Please prepare a small PBIX example containing only the relevant columns, using the original model structure.
Save it to a public cloud service and share the link .
So true_origin and true_destination are both connected to a table named invoice_details as follows:
[invoice_details[b_location_hierarchy_origin] <— true_origin[a_location_hierarchy]]
[invoice_details[c_location_hierarchy_destination] <— true_destination[d_location_hierarchy]]
I have also provided the following example table for how all six columns/measures look together:
| Origin_City_Name | a_location_hierarchy | b_location_hierarchy_origin | c_location_hierarchy_destination | d_location_hierarchy | Destination_City_Name |
| Tokyo | 6056 | 6056 | 7359 | 7359 | Tokyo |
| New York City | 7417 | 7417 | 11372 | 11372 | Paris |
| Paris | 11204 | 11204 | 2918 | 2918 | New York City |
| Sydney | 2246 | 2246 | 4434 | 4434 | Rio de Janeiro |
| Cape Town | 2938 | 2938 | 10616 | 10616 | Cape Town |
| Rio de Janeiro | 4960 | 4960 | 1788 | 1788 | Sydney |
| London | 7653 | 7653 | 9054 | 9054 | Cairo |
| Istanbul | 6664 | 6664 | 3959 | 3959 | Toronto |
| Toronto | 2256 | 2256 | 3941 | 3941 | Bangkok |
| Bangkok | 11102 | 11102 | 8784 | 8784 | Istanbul |
Hope this can give you some ideas.