Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Here is a picture illustrating my scenario:
I read that the proper relations between the two source is the key but I don't know how to connect these two different sources.
If I try to merge the two tables in one - is this a good approach...I will have table with 250K recoords.
Can anyone advise me what is the recommended approach is such scenarios?
Solved! Go to Solution.
@DimchoTsanov
The best practice and approach is to create separate dimension tables, either in SQL or Power Query. For example, you can create a single date table and link to both the source data tables using the One-To-Many relationship.
Follow the same for the other columns that are common in both tables.
⭕ Subscribe and learn Power BI from these videos
⚪ Website ⚪ LinkedIn ⚪ PBI User Group
@DimchoTsanov
The best practice and approach is to create separate dimension tables, either in SQL or Power Query. For example, you can create a single date table and link to both the source data tables using the One-To-Many relationship.
Follow the same for the other columns that are common in both tables.
⭕ Subscribe and learn Power BI from these videos
⚪ Website ⚪ LinkedIn ⚪ PBI User Group
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
109 | |
98 | |
77 | |
66 | |
54 |
User | Count |
---|---|
144 | |
104 | |
101 | |
86 | |
64 |