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.
I am writing DAX queries with large and multiple tables and the query is internally generating CallbackDataID which is believed to be detrimental to performance.
Is there any way to write a query that can bypass that? @marcorusso
@AlexisOlson @CNENFRNL @bcdobbs @OwenAuger
Thank you in advance.
A sample query is attached in the pbix.
Base table
| Continent | Country | Province | Value |
|-----------|---------|----------|-------|
| NA | CA | AB | 100 |
| NA | CA | AB | 50 |
| NA | CA | ON | 1000 |
| NA | CA | ON | 20 |
| NA | CA | SK | 400 |
| NA | CA | SK | 4000 |
Desired
| Continent | Country | Province | Value |
|-----------|---------|----------|-------|
| NA | CA | AB | 50 |
| NA | CA | ON | 20 |
| NA | CA | SK | 400 |
Query plan
Have you read this ? Formula engine and storage engine in DAX - SQLBI
or this Performance Issue In DAX Studio: CallBackDataID - Enterprise DNA
Here is a version that doesn't use CallbackDataID:
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 |
---|---|
111 | |
100 | |
80 | |
64 | |
58 |
User | Count |
---|---|
148 | |
111 | |
93 | |
84 | |
66 |