LinkedIn
Twitter
Beginning with Looker 4.8, we introduced a new model level parameter called fiscal_month_offset:. This will allow you to define when your fiscal year begins for each model if you don’t use the calendar year for your quarters. To set your fiscal year, navigate to your model file and include this parameter like so:
New LookML
connection: thelook
### INCLUDES ###
include: "*.view.lkml"
include: "*.dashboard.lkml"
fiscal_month_offset: 1
Old LookML
- connection: thelook
### INCLUDES ###
- include: "*.view.lookml"
- include: "*.dashboard.lookml"
- fiscal_month_offset: 1
Here, we defined our offset to be 1 month and assuming the calendar year starts in January, our new fiscal year will begin in February and our fiscal Q1 will include February, March, and April.
##Fiscal Year Timeframes
We also introduced four new fiscal timeframes for the dimension_group field:
fiscal_year, fiscal_quarter, fiscal_month_num, and fiscal_quarter_of_year
####New LookML
dimension_group: created {
type: time
timeframes: [date, month, year, quarter, fiscal_year, fiscal_quarter, fiscal_month_num, fiscal_quarter_of_year]
sql: ${TABLE}.created_at
}
Old LookML
- dimension_group: created
type: time
timeframes: [date, month, year, quarter, fiscal_year, fiscal_quarter, fiscal_month_num, fiscal_quarter_of_year]
sql: ${TABLE}.created_at
What is really cool is that the fiscal_month_offset: parameter only affects the fiscal_* timeframes. So if you’d like, you can have your fiscal and calendar timeframes all in one dimension_group like above. As you can see below, when we have our offset set at 1, January appears in Q4 for our fiscal quarter but Q1 in the calendar quarter.
##Filtering
If you wanted to use matches advance on one of those timeframes, as of now, we introduced two new intervals, fiscal year and fiscal quarter. For example, we can write something like 2 fiscal years ago to grab data from 2 fiscal years ago, like so:
