Symptom
- Setting a filter using a Dynamic Date Variable returns no results. E.g. "Equal to Today's Date" or "Greater than Today's Date" brings no data.
- Entering a specific date, e.g. 1/1/2018, will return data
Environment
SAP SuccessFactors Workforce Analytics
Cause
Server Timezone
Resolution
Please note that the Dynamic Date fields consider server time and not a user's local timezone.
For example, if you are logged in 12:11 PM EST on December 1 and expect that the system will fetch Today's date as December 1 this will depend on the Data Center the instance is in.
If the instance is in DC10 which is in Sydney (AEDT), the the current date/time will be December 2 at around 3:30 AM. So the filter using Dynamic Date will consider December 2 as Today's date. E.g. Hire Date Equals To Today's Date (December 2) and NOT " = 12/1/2018".
If there are no records with 12/2, the query will return blank results.
So it is important to consider server time when designing the query or when configuring a Scheduled job which depends on dynamic dates like "Today", because ORD Live Data and Advanced Reporting considers server time for system dates.
Keywords
dynamic date variables, date fields, filter for today's records, system time, data center timezone, advanced reporting date filter , KBA , LOD-SF-ANA-ADV , Advanced Reporting (ODS) , Problem