Open mestachs opened 4 years ago
@abyot can you help me answering this question ?
Hello,
Sorry for the late response. The question you posted is a desired feature. The aggregation considers a financial period scheme where the start of the current year is the 11'th month of the previous year. For example, the start date for "2012Q1" is "2019-07-08" which converted to Ethiopian calendar becomes, 2011-11-01. The same goes for Financial yearly periods as well. The starting of the year 2012 is 2011-10-01.
Hence why you are getting a period like this.
| iso | startdate | enddate | yearly | quarterly | |--------+-------------+------------+----------+-------------| | 2012Q1 | 2019-07-08 | 2019-10-11 | 2011 | 2012Q1 | | 2012Q2 | 2019-10-12 | 2020-01-09 | 2012 | 2012Q2 | | 2018Q4 | 2026-04-09 | 2026-07-07 | 2018 | 2018Q4 |
Hope this helps.
Hello, Thanks for the work.
I tried your implementation for amharic calendar, looks to support 2 months offset for quarter/months.
But I noticed that in db, the year referenced in the _periodstructure is still the one for "month"
same for months
I would have expected 201111 and 201112 as it's in 2012Q1 to end up in "2012" analytics summation/averages.
is this the desired "feature" or a "limitation/omission" ?
Thanks for the clarification