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.
Hi,
The way I'm joining and merging my data is creating millions of rows to process and it takes hours to compute anything. There must be a better way!
My data is from the real estate development industry.
Solved! Go to Solution.
Hi @Kashuo,
Any changes in one query (table) will be applied to the related merged query. That’s why it takes so much time. Adding a calculated column of the earliest date to the table respectively would be a good practice.
1. In order to simply the model, it keeps the essential columns.
2. The relationships are clear.
3. Add a column in table “Floor” with this formula.
Earlist_Opening_Date_Each_Floor = calculate(min('Zone'[opening_date]))
4. Add a column in table “Property” with this formula.
Earliest_Date_Each_Porperty = CALCULATE(min('Floor'[Earlist_Opening_Date_Each_Floor]))
Best Regards!
Dale
Hi @Kashuo,
Any changes in one query (table) will be applied to the related merged query. That’s why it takes so much time. Adding a calculated column of the earliest date to the table respectively would be a good practice.
1. In order to simply the model, it keeps the essential columns.
2. The relationships are clear.
3. Add a column in table “Floor” with this formula.
Earlist_Opening_Date_Each_Floor = calculate(min('Zone'[opening_date]))
4. Add a column in table “Property” with this formula.
Earliest_Date_Each_Porperty = CALCULATE(min('Floor'[Earlist_Opening_Date_Each_Floor]))
Best Regards!
Dale
Hello again,
This worked for a while, but no longer.
Now I'm getting Circular Dependency Errors when I use Calulate. If I take out the "calculate" then the circular dependency error goes away, but then the min gives me an absolute minumum (the first date ever), rather than the earliest date per floor.
If I use a measure, then the tabular view gives me the earliest date per floor, but then I can't use Measures in the date slicers at the bottom of my sheet.
Any idea how to remove the Circular Dependency? Other than using a measure like this thread suggests?
Hi @Kashuo,
Could you please open a new thread? Because the new issue isn't related to this topic, which would be hard for others to search solutions in this community.
Could you please provide more information in the new thread?
1. A little sample;
2. The formula you already tried to use;
3. The result you want to get from this formula. (maybe we can create a new one.)
Best Regards!
Dale
This worked perfectly, thank you so much!
Hi,
My data is from the real estate development industry.
Hi @Kashuo
Any changes in one query (table) will be applied to the related merged query. That’s why it takes so much time. Adding a calculated column of the earliest date to the table respectively would be a good practice.
1. In order to simply the model, it keeps the essential columns.
2. The relationships are clear.
3. Add a column in table “Floor” with this formula.
Earlist_Opening_Date_Each_Floor = calculate(min('Zone'[opening_date]))
4. Add a column in table “Property” with this formula.
Earliest_Date_Each_Porperty = CALCULATE(min('Floor'[Earlist_Opening_Date_Each_Floor]))
Best Regards!
Dale
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 |
---|---|
115 | |
100 | |
88 | |
68 | |
61 |
User | Count |
---|---|
152 | |
120 | |
102 | |
87 | |
68 |