You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some fiscal years are tracked differently, needing support of a negative shift year.
For example, in one scenario a date_day of 2022-01-01 is actually in the fiscal year 2023. The generated fiscal_year_number would need to be 2023 in this case. This can be achieved by suppling a negative shift value however, doing so causes the rendered SQL to be interpreted as a comment:
Some fiscal years are tracked differently, needing support of a negative shift year.
For example, in one scenario a
date_day
of2022-01-01
is actually in the fiscal year 2023. The generatedfiscal_year_number
would need to be2023
in this case. This can be achieved by suppling a negative shift value however, doing so causes the rendered SQL to be interpreted as a comment:Gets rendered as:
Not sure how everyone else's use case differs, but I thought I would bring it up in case there are more similar scenarios out there.
The text was updated successfully, but these errors were encountered: