User Guide

To help get you started, a sample .pbix file is available to download on AppSource. This doesn't require a licence and includes examples of common use-cases that can be adapted to your requirements. If, however, this isn't clear and you require support, don't hesitate to contact us using the form or email address shown in the footer.

General Recommendations:

1) Although not strictly necessary, it is always suggested to create a dedicated calendar table, especially when trying to leverage time-intelligence functions in DAX. The sample file is setup this way - refer to it if needed.

2) The sample file uses dedicated Display and Range Year tables for the purposes of allowing user customisability with slicers. If desired, you can simplify this step by using Display/Range Year measures that have your desired cut-offs directly. For example, the Display Year measure could be defined as:

Display Yr = SELECTEDVALUE('Calendar'[Year]) >= YEAR(TODAY())

This approach ensures that the charts will automatically update as you roll into new calendar years without requiring any manual modification of existing reports.

3) When using weekly data and the corresponding WEEKNUM axis value, you will likely want to apply a filter to the Calendar table to ignore entries with a value of 53 resulting from leap years.

4) In your y-axis value measure, take care to consider what is an appropriate aggregation strategy in case of multiple values occurring for the given year and x-axis label. For time-series data, you may need to resample datapoints with the use of AVERAGEX, LASTDATE etc.

5) If you provide a date-type column directly as the x-axis, the visual can align these dates for you automatically (when enabled in the settings). If, however, you prefer to manage this yourself, create a new calculated column on the calendar table using the following:

Date Rebased = DATE(1970, MONTH([Date]), DAY([Date]))

Now use this column as the new x-axis labels field to achieve the same result as the in-built visual functionality.