Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredPower BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.
I may be totally off-base here in my approach, but here is my situation.
I have a measure (albeit, likely not a good measure) that gets me this correct value:
Account Renewal Rate T3M = CALCULATE([% Accounts Renewed], FILTER(ACCOUNT_ANALYSIS, ACCOUNT_ANALYSIS[Trailing Months LRD]<=-1 && ACCOUNT_ANALYSIS[Trailing Months LRD] >=-3))
The goal was to get a measure not relying on visual filters to calculate the aggregate prior 3 months (April, May, June)'s renewal rate.
The Trailing Months LRD (Last Renewal Date) uses this workaround to identify the prior 3 full months; other calculations I tried were including July numbers, which is not correct for this instance.
I am using a date table, but it is connected to a different date field not relevant to this current situation.
Now, looking at future accounts and dates, which is a different date field, I want to use the Account Renewal Rate T3M value to multiple by these numbers in the table to get a projected rate of renewal:
In other words, 516 * 0.6310 = 326 accounts are projected to renew.
But I end up getting this, which is not correct, and obviously shows some blank rows:
So I'm guessing this is a filtering (visual or measure) or date problem, as these tables are using two different date perspectives and filtering respectively. I simply want the value from my measure to use as a multiplier.
In a prior iteration, we just hardcoded the trailing 3 months value (e.g., Measure = 0.6310) but I'd like to make this dynamic so I don't have to update it each month.
Any thoughts? Thanks in advance!
if it's a different date field in a different table (but there's a relationship between these two tables) you may find that the filtering you're applying on one table is feeding through the relationship you have, causing a 'correct data' filtering with what you're trying to display but a wrong outcome for you.
Is it possible to count the open eligible accounts (or sum whichever formula)?
It would be something like the following:
Expected Account Renewal =
VAR __EligibleAccounts = CALCULATE(COUNT(Table1[ID]), FILTER (Table1, Table1[ID] = Table2[ID]))
RETURN
__EligibleAccounts * [Account Renewal Rate T3M]
You can create a custom column with the variable as well which you could use to show the values next to the measure. You should be able to replicate the [Open Eligible Accounts] column inside of your other table. The __EligibleAccounts would need to flex between count/sum/countrows depending on your data requirements.
This method would ensure that you're not being hindered by a relationship issue because you're consolidating the data into a singular table, and then you can explore changing your filtering options.
Thanks for your response! All of my data is within the same table 🙃 but this is giving me something to think about, maybe I need separate the data into their own tables (Past vs. Future, Renewed vs. Upcoming).
I did try a custom column that simply references the measure, but this didn't work. I'll keep trying some different methods.
User | Count |
---|---|
84 | |
77 | |
76 | |
43 | |
36 |
User | Count |
---|---|
109 | |
56 | |
52 | |
45 | |
43 |