☰

Updated Adding Custom Time Periods (markdown)

Joseph Adams committed 2015-03-04 16:18:27 -0500 commit 2ed0d9ebafb8fe0ca2b44e9ecc545a7cc6c00151

				FAQ/Questions/Adding-Custom-Time-Periods.md
			
          @@ -21,7 +21,7 @@ if (!AdHocSettings.CustomTimePeriods.ContainsKey("Lunar Cycle")) {

           }

           ```

          -Since we didn't specify a **StartDate**, Izenda will assume the server's current date and time as the **StartDate** of the time period. If we run a report with an **in time period** filter on OrderDate that used **lunar cycle** as its time period on March 4, 2015 at 3:46:58 PM, the query results of this would like similar to the below SQL:

          +Since we didn't specify a **StartDate**, Izenda will assume the server's current date and time as the **StartDate** of the time period. If we run a report with an **in time period** filter on OrderDate that used **lunar cycle** as its time period on March 4, 2015 at 3:46:58 PM, the query results of this would look similar to the below SQL:

           ```sql

           SELECT TOP 100000

...	...	@@ -21,7 +21,7 @@ if (!AdHocSettings.CustomTimePeriods.ContainsKey("Lunar Cycle")) {
21	21	}
22	22	```
23	23
24		-Since we didn't specify a StartDate, Izenda will assume the server's current date and time as the StartDate of the time period. If we run a report with an in time period filter on OrderDate that used lunar cycle as its time period on March 4, 2015 at 3:46:58 PM, the query results of this would like similar to the below SQL:
	24	+Since we didn't specify a StartDate, Izenda will assume the server's current date and time as the StartDate of the time period. If we run a report with an in time period filter on OrderDate that used lunar cycle as its time period on March 4, 2015 at 3:46:58 PM, the query results of this would look similar to the below SQL:
25	25
26	26	```sql
27	27	SELECT TOP 100000