https://community.qlik.com/t5/App-Development/Master-calendar-saved-data-vs-expressions/m-p/1542898#M39158 <P>I am wondering which of the following implementations for detailed date info might boost performance:</P><P>1. The common master calendar, which saves all the fields within a table</P><P>2. Having only a [Date] field in the calendar table, and creating one master dimension for each of the previous fields, with the corresponding formula</P><P>&nbsp;</P> Sat, 16 Nov 2024 06:37:07 GMT gmenoutis 2024-11-16T06:37:07Z https://community.qlik.com/t5/App-Development/Master-calendar-saved-data-vs-expressions/m-p/1542898#M39158 <P>I am wondering which of the following implementations for detailed date info might boost performance:</P><P>1. The common master calendar, which saves all the fields within a table</P><P>2. Having only a [Date] field in the calendar table, and creating one master dimension for each of the previous fields, with the corresponding formula</P><P>&nbsp;</P> Sat, 16 Nov 2024 06:37:07 GMT https://community.qlik.com/t5/App-Development/Master-calendar-saved-data-vs-expressions/m-p/1542898#M39158 gmenoutis 2024-11-16T06:37:07Z https://community.qlik.com/t5/App-Development/Master-calendar-saved-data-vs-expressions/m-p/1543095#M39174 <P>I don't see any benefits of implementing 2. and 1. is quite common in nearly all use-cases.</P><P>- Marcus</P> Tue, 12 Feb 2019 14:39:10 GMT https://community.qlik.com/t5/App-Development/Master-calendar-saved-data-vs-expressions/m-p/1543095#M39174 marcus_sommer 2019-02-12T14:39:10Z