Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowTry your skills in the Power BI Dataviz World Championship! Round one ends June 26. Join now
Hello PBI Experts,
I am having a problem with creating a column using DAX.
Kindly check what is wrong with below DAX:
All other values are blank.
BR,
Jorge
Solved! Go to Solution.
Hi @JorgeAbiad - You need to remove the overlap by ensuring each date range is distinct. Also, correct the third condition to use date2 for January–July 2025.
License Limit =
VAR date0 = {DATEVALUE("April 2024"), DATEVALUE("May 2024"), DATEVALUE("June 2024"), DATEVALUE("July 2024"), DATEVALUE("August 2024"), DATEVALUE("September 2024")}
VAR date1 = {DATEVALUE("October 2024"), DATEVALUE("November 2024"), DATEVALUE("December 2024")}
VAR date2 = {DATEVALUE("January 2025"), DATEVALUE("February 2025"), DATEVALUE("March 2025"), DATEVALUE("April 2025"), DATEVALUE("May 2025"), DATEVALUE("June 2025"), DATEVALUE("July 2025")}
RETURN
SWITCH(
TRUE,
'Consolidated_AS-ONE'[D365 Base]="D365 Sales Enterprise" && 'Consolidated_AS-ONE'[Status Date].[Date] IN date0, 300,
'Consolidated_AS-ONE'[D365 Base]="D365 Sales Enterprise" && 'Consolidated_AS-ONE'[Status Date].[Date] IN date1, 500,
'Consolidated_AS-ONE'[D365 Base]="D365 Sales Enterprise" && 'Consolidated_AS-ONE'[Status Date].[Date] IN date2, 600,
'Consolidated_AS-ONE'[D365 Base]="D365 Team Member", 30,
'Consolidated_AS-ONE'[D365 Base]="D365 Marketing", 100
)
Now, July 2025 will get the correct value of 600, as it is only included in date2. This should resolve the issue of incorrect values for July. Hope this helps in your scenerio
Proud to be a Super User! | |
Hi @JorgeAbiad - You need to remove the overlap by ensuring each date range is distinct. Also, correct the third condition to use date2 for January–July 2025.
License Limit =
VAR date0 = {DATEVALUE("April 2024"), DATEVALUE("May 2024"), DATEVALUE("June 2024"), DATEVALUE("July 2024"), DATEVALUE("August 2024"), DATEVALUE("September 2024")}
VAR date1 = {DATEVALUE("October 2024"), DATEVALUE("November 2024"), DATEVALUE("December 2024")}
VAR date2 = {DATEVALUE("January 2025"), DATEVALUE("February 2025"), DATEVALUE("March 2025"), DATEVALUE("April 2025"), DATEVALUE("May 2025"), DATEVALUE("June 2025"), DATEVALUE("July 2025")}
RETURN
SWITCH(
TRUE,
'Consolidated_AS-ONE'[D365 Base]="D365 Sales Enterprise" && 'Consolidated_AS-ONE'[Status Date].[Date] IN date0, 300,
'Consolidated_AS-ONE'[D365 Base]="D365 Sales Enterprise" && 'Consolidated_AS-ONE'[Status Date].[Date] IN date1, 500,
'Consolidated_AS-ONE'[D365 Base]="D365 Sales Enterprise" && 'Consolidated_AS-ONE'[Status Date].[Date] IN date2, 600,
'Consolidated_AS-ONE'[D365 Base]="D365 Team Member", 30,
'Consolidated_AS-ONE'[D365 Base]="D365 Marketing", 100
)
Now, July 2025 will get the correct value of 600, as it is only included in date2. This should resolve the issue of incorrect values for July. Hope this helps in your scenerio
Proud to be a Super User! | |
Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.
Check out the May 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 22 | |
| 21 | |
| 21 | |
| 20 | |
| 13 |
| User | Count |
|---|---|
| 59 | |
| 53 | |
| 40 | |
| 31 | |
| 26 |