As you can see, you would be able to set overall volume of periods, or if you wanted to have it shared amongst different components, you're given options for that. Do you want to see the change value or the percent change? The user would be able to make adjustments and customizations and capture it in their bookmark. And that date range comparison can be applied to both charts as well as crosstab tables. So this way, you can get the types of comparisons that you want to have visually, whether it's the flat details in the table or having more of that graphical perspective. The end user experience with creating the date range comparison will match what the designers and the developers are going to have when initially setting up a date range comparison.
All you need to get started with creating a date range comparison is a chart or a crosstab with a date field and some form of measure, some metrics, some calculation that you're working on, and then you're able to do a right click date range comparison. You can choose very specific custom periods that you want to compare, maybe it's that you want to have a certain volume of years and that you want to break down by week and show just the percent change. Depending on the combinations that you have selected, you might have other dimensions that you've factored into your chart it will just trigger default styling that should mirror what is going to be the most common, most popular and optimal way to visualize this type of comparison.
Now this particular dashboard has historical data of 2012, 2013, 2014 type data, so if I were to do only the last few years I'm actually going to trigger a warning that there's no data for the range that I've actually selected. So this is something where you're going to get that visual feedback of hey, it's an empty chart, you can jump back into your range comparison maybe up, you know, the periods that you want to have available. And once you do that, it's like oh, hey, you know, I can do the change differential for 2012 and 2013.