One of the widgets I've built is a line graph showing number of donors and amount in dollars per year. One of the problems I'm encountering is an inaccurate drop-off in whatever the most recent year is on the graph. In the first photo below, the most recent year is 2019 and both line values to close to the 2k mark. But notice, in that same photo, that the 2018 values of both lines are 3.5k+. Yet when I change the filter so the most recent year is 2018, instead of showing 2018 line values at 3.5k+, it shows the same drop-off as seen in the first photo. It seems no matter the most recent year shown on the graph, they all have the same drop-off despite having other real data points that should be showing instead.
Has anyone seen this and is there a fix I missed? Thanks!
Photo one - 2019
Photo two - 2018
Photo three - 2017
From what you are showing I'm not clear which date you are filtering by current fiscal year. Are you doing the campaign date, Expiration Date, Or one of the other dates?
You can tell which year are filtering on by You can tell which date by hovering over the label "Fiscal Current Year Offset"
One of the ways I debug a situation like this is to turn the line graph into a pivot table. Then filter by the different fiscal years to try to tell what is going on here.
Hi, .
The Current Fiscal Year Offset filter is pulling off the of the contribution date table. Thank you for recommending changing the widget from a line graph to a pivot table. Even though I don't know the cause or solution, it's much easier to see the raw numbers. Below are three photos of the pivot table showing what I described above with specific numbers. At bottom I've also included the .dash file for what I'm working with, though it's worth noting this problem occurs on other dashboards I work with.
2019 as the most recent fiscal year. In this snapshot, notice the 2018 values.
Now with 2018 as the most recent fiscal year, notice the change in 2018 values. And again for 2017.
2017 as the most recent fiscal year.
.dash file: CSA AnnualFundPerformance.dash..dash
,
I can reproduce a similar behavior in my Tessitura Analytics. I'm not clear why this is occurring. I'd like to invite you to open a support ticket, with the great detail you have provided here in this thread. If you have found a bug, It would be great to get this information into the development team.
In the meantime, as a workaround, you might change from the contribution date displayed as a year to the "fiscal year offset" value or Contribution Date "Fiscal Year" value. Rather than formatting the date as a year.
cc: Chris Wallingford
Hi Taylor,
Looks like you have Calendar "Years in Date" on your axis, against which you're filtering by Fiscal Year. Every time you change your fiscal filter, you're cutting some number of months that final calendar year.
Hope that makes sense,Chris
Thanks, Chris! I switched the X-axis filter to contribution fiscal year. Problem solved!