It would be very useful if we could set our fiscal year somewhere and have that utilised by charts. This could possibly be done either as a global setting or per chart. Currently to display fiscal year in a coherent way on visualisations we have to add a custom column to our date tables that will generate an appropriate label for charts e.g. (01) - Oct, (02) - Nov if your fiscal year starts in Oct. It would be much friendly if we could instruct visualisations where our fiscal year begins and have them intelligently label axis. I've noticed that if you are using a date field on the axis then visuals will change the labels based on various factors. For example for a certain period it may show individual dates, or months, or years depending on the size of the chart and other factors. This doesn't work with custom labels though and because you cannot add two labels to an axis e.g. months AND years I cannot have a chart easily stretch and represent a period longer than a year when using fiscal year labels. Hope this makes sense :-)
26 Comments
- Many organisations have fiscal year ends which differ from their calendar year end. Is it possible to customise the slicer with an option to show years and quarters for a fiscal year end for e.g. like 30 Sept?
- We want to show months according to the fiscal month number rather calendar month number. When we populated the data in a table visualization it was ordered according to the fiscal month number. But when we switched to graphs the ordering changed according to calendar year
- You can already do this. Add a numerical column to your Date table that defines the sorting order you need, and use the 'Sort by Column' feature.
- The Timeline custom visual must support Fiscal Years just the way Datazen does. The system could ask for the fiscal start date and calculate accordingly.
- yes, a fiscal year slicer that allows the user to set the fiscal year beginning month would be very helpful. the option to show fiscal year quarters would be an added bonus.
- Drilling down into fiscal year would be useful. Data can currently only be represented in fiscal year order if you sacrifice the ability to use the date functions.
- Please any BI developer or Power BI team have look at this problem and suggest me solution or Power BI team please make this your next up gradation in your tool it is too higher in priority for Visula Dashboard. Tableau has this feature in built but i am die heart fan of Microsoft tool and want to use always this.
- I want to change default fiscal year of power Bi as per client requirement and i also need drilling down into fiscal year to get information at every layer.
- In the Xero reports, if you select a fiscal year which is July to June, the report displays as January to December. So the data goes Jan 2016 -> June 2016 then July 2015 -> December 2015.
StrubkjMicrosoft Employee
Hi there. While I agree that there should be some easy setting to adjust FY settings other than Jan-Dec, if you are already setting up a date table either that you link to your data set or configure using a calculated table, you can do this quite easily on your own, with just a little DAX. Here is one I use to create a column reflecting my organizations FY (July-June): DateFY = IF(DateKey[DateMonthNumber] > 6, DateKey[CY Year] + 1, DateKey[CY Year]) After setting up a calculated date dimension table with a Calendar Year column and a month number column, you realign your Fiscal Year, as shown above. If you are working with very large datasets, might be best to configure a date dimension table in another source, and connect to it to save on memory consumption. Of course, as calculated column value, you can use it as a filter or use is as your configured Fiscal year, Fiscal quarter, month, and day values in your shared axis of a graph to customize your drill down. It's a bit more complicated than it needs to be, and it would be nice to be able to just adjust the native setting in your Power BI Desktop to have your date values reflect your FY FQ needs, but give the above a try. It works well enough for me!
