The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
I literally copied a visualization and used different data sets with identical field and data structures, but I'm getting a different outcome in the visualization.
We're pulling our Azure and AWS hosting costs for month over month % change trend in the last quarter.
Both data sets are updated daily. The MoM% was calculated identically, the vis filters are set identical (last 3 calendar months) however as you can see in below screenshots that one viz shows current month (April) + previous two, while the other viz shows the previous 3 months (not April).
Again, both data sources are updated daily, and both have data for the current month.
Quick edit, here are the MoM% formulas:
AWS Cost MoM% =
IF(
ISFILTERED('DateTable'[Date]),
ERROR("Time intelligence quick measures can only be grouped or filtered by the Power BI-provided date hierarchy or primary date column."),
VAR __PREV_MONTH =
CALCULATE(
SUM('AWS Util'[AWS Cost]),
DATEADD('DateTable'[Date].[Date], -1, MONTH)
)
RETURN
DIVIDE(SUM('AWS Util'[AWS Cost]) - __PREV_MONTH, __PREV_MONTH)
)
And the Azure MOM:
Az Cost MoM% =
IF(
ISFILTERED('DateTable'[Date]),
ERROR("Time intelligence quick measures can only be grouped or filtered by the Power BI-provided date hierarchy or primary date column."),
VAR __PREV_MONTH =
CALCULATE(
SUM('Az Util'[Az Cost]),
DATEADD('DateTable'[Date], -1, MONTH)
)
RETURN
DIVIDE(SUM('Az Util'[Az Cost]) - __PREV_MONTH, __PREV_MONTH)
)
Solved! Go to Solution.
Jeez - nevermind, just answered my own question with this post. Will leave for posterity in case anyone needs it for reference:
DATEADD('DateTable'[Date].[Date], -1, MONTH)
Was the issue in the AWS calculation. Thought I had removed it, but apparently not. For whatever reason the [Date].[Date] vs just [Date] will evaluate current month....
Jeez - nevermind, just answered my own question with this post. Will leave for posterity in case anyone needs it for reference:
DATEADD('DateTable'[Date].[Date], -1, MONTH)
Was the issue in the AWS calculation. Thought I had removed it, but apparently not. For whatever reason the [Date].[Date] vs just [Date] will evaluate current month....
Hi @RyanBrantley ,
Thank you for your sharing, I'm sure it will provide reference for many people,. I suggest that you mark your replies as answers so that people can search for this post faster.
Best Regards,
Dedmon Dai