Hi Andrea Boriero, Thanks for the workaround. Renaming the year attribute solved the issue in my environment as well.