Tenant Settings
Tenant settings define information about the tenant, including the data start and end dates.
Access requirements
Profiles: Data Engineer
Reach out to your administrator for access.
Overview
To access tenant settings, open a project and navigate to Data > Tenant Settings. After you select a tenant, you can change the start date type, the start date explicit date or month offset, the end date config type, and enable or disable end date overrides.
Start date type
Set the date that the tenant data starts from. The tenant start date can be fixed or rolling. If fixed, select an explicit start date that the data begins from. If rolling, set the number of months to offset data from.
Example: Fixed start date
Let’s say you have a tenant called Jupiter. In the Jupiter tenant, you want your data in Visier to start from January 2019 and end at the last date found in the most recent data transfer. To do so, you would navigate to Data > Tenant Settings and apply the following tenant settings:
- Start date type: Fixed start date
- Start date explicit date: January 1, 2019
- End date config type: Auto detect from data
This ensures that Visier loads data for Jupiter beginning on January 1, 2019 up until the most recent date in your data.
End date config type
The end date config type sets the upper limit of selectable time periods in the solution experience. For example, if the end date config type is End of previous month and the current month is February, your users can select data up to the end of January in analyses and visualizations.
You can set the end date config type at the tenant level and per analytic object.
- Tenant level: The end date config applies to all analytic objects.
- Per analytic object: Overrides the tenant end date config for a specific analytic object.
Example: Let's say you load Employee data on the 15th of every month, Applicant data every Wednesday, and Requisition data every Friday. In this example, Applicant and Requisition have new data every week, whereas Employee has new data once a month. We can set the tenant end date config type as End of previous week, and then set an end date override for Employee as End of previous month. This allows your users to select dates up to the end of the previous week for Applicant and Requisition, and up to the end of the previous month for Employee. Without the Employee override, users could select dates for Employee up to the end of the previous week, but Employee data isn't loaded weekly so the visualizations would be blank.
To override the tenant end date config type for a specific analytic object:
- In a project, on the navigation bar, click Data > Tenant Settings.
- Select a data category.
-
In Settings, turn on Enable end date overrides on individual analytic objects.
Tip: If disabled, all analytic objects use the latest upload to determine the data end date. If enabled, each analytic object uses the latest upload for data that populate the object. For objects that aren't updated frequently, we recommend that you set object's end date config type to Use timestamp of source for a specific analytic object.
Let's say you loaded Employee Engagement data on July 31 and Employee data on September 20. Enable end date overrides on individual analytic objects is turned on, but there are no overrides for Employee Engagement or Employee specifically. Both objects use the tenant-level end date config type, but Employee Engagement uses July 31 as the latest upload, whereas Employee uses September 20 as the latest upload. If the tenant-level end date config type is End of previous month, then Employee Engagement's end date is June 30 and Employee's end date is August 31.
- On the navigation bar, navigate to Model > Analytic Objects.
- Select an analytic object.
- In Settings, under Data version settings, turn on Use default.
- In End date config type, select an end date config type from the list.
The following table describes each of the end date config types.
Each example in the table assumes today is June 29 and the last data processing job ran on June 9. The examples show the latest date you can select in an analysis for three upload scenarios: an upload on April 30, an upload on May 2, and an upload on June 9.
|
End date config type |
Description |
Example: Latest selectable date in analyses |
|---|---|---|
|
Auto detect from data |
Use the date of the latest data point in the upload, including dates in the future. For example, let's say the latest data point in each example upload is April 30, July 1, and June 30, respectively. We recommend Auto detect from data as the default tenant-level end date config type. |
|
|
End of current month |
Use the last day of the month of the latest upload. |
|
|
End of previous day |
Use the day before the latest upload. |
|
|
End of previous week |
Use the most recent Sunday before the latest upload. |
|
|
End of previous month |
Use the last day of the month before the latest upload. |
|
|
Use source timestamp |
Use the exact time of the latest upload. |
|
|
Use timestamp of source for a specific analytic object |
Use the exact time of the latest upload that contains the data for a specified analytic object. For example, use the time of the latest upload for Employee data. Let's say the latest Employee upload was on March 8. |
The end date is March 8 for all three example uploads because the latest Employee upload was March 8. |
|
Use timestamp of current run |
Use the current time as of when the loaded data version was generated. |
The end date is June 9 for all three example uploads because the last data version was generated on June 9. |
|
End of current day |
Use midnight at the end of the latest upload day. |
|
|
End of previous month (if first load of month) or previous day |
Use the last day of the previous month if the upload is the first of the month. Otherwise, use the day before the upload. For example, let's say that April 30 isn't the first upload of the month, May 2 is the first upload of the month, and June 9 isn't the first upload of the month. |
|
|
End of previous month (if first load of month) or week |
Use the last day of the previous month if the upload is the first of the month. Otherwise, use the end of the previous week. For example, let's say that April 30 isn't the first upload of the month, May 2 is the first upload of the month, and June 9 isn't the first upload of the month. |
|
|
End of previous month (if first load of month) or use source timestamp |
Use the last day of the previous month if the upload is the first of the month. Otherwise, use the exact time of the latest upload. For example, let's say that April 30 isn't the first upload of the month, May 2 is the first upload of the month, and June 9 isn't the first upload of the month. |
|
|
End of current month (if last day) or previous month |
Use the last day of the current month if the upload happens on the last day of the month. Otherwise, use the last day of the previous month. |
|
|
End of previous month (if first load of month) or current month |
Use the last day of the previous month if the upload is the first of the month. Otherwise, use the last day of the current month. For example, let's say that April 30 isn't the first upload of the month, May 2 is the first upload of the month, and June 9 isn't the first upload of the month. |
|
|
Allow future data |
Use the furthest date in the upload. For example, let's say there is a future start date of July 1 in all example uploads. Caution: Do not use for subject and overlay data. |
The end date is July 1 for all three example uploads because a future start date of July 1 exists in each upload. |
|
Last specified day of the week |
Use the most recent specified weekday before the latest upload, such as the latest Wednesday. |
|
|
Later or last specified day of the week or end of previous month |
Use the most recent specified weekday before the upload without going beyond the previous month, such as the latest Wednesday. |
|
|
End of current month (if within five business days to end) or previous month |
Use the last day of the current month if the upload falls within five business days of month end. Otherwise, use the last day of the previous month. |
|
|
End of previous month (if first load of month) or last specified day of the week |
Use the last day of the previous month if the upload is the first of the month. Otherwise, use the most recent specified weekday, such as the latest Wednesday. In this example, let's say that April 30 isn't the first upload of the month, May 2 is the first upload of the month, and June 9 isn't the first upload of the month. |
|
The following groups show how each end date config type determines its result. For the exact behavior and examples, see the table above.
Use the exact moment of upload
- Use source timestamp: Exact time the upload happened.
- Use timestamp of current run: Exact time the data version was generated. This is not necessarily the upload time.
- End of current day: Midnight at the end of the upload day.
- End of previous day: Day before the upload.
Use a calendar boundary near the upload
- End of previous week: Most recent Sunday on or before the upload.
- End of current month: Last day of the upload's month.
- End of previous month: Last day of the month before the upload.
- Last specified day of the week: Most recent chosen weekday (e.g., latest Wednesday) before the upload.
Use the data, not the upload date
- Auto detect from data: The latest date actually found in the file, even future-dated. We recommend this as the default tenant-level end date config type.
- Allow future data: Same as Auto detect from data, but explicitly permits dates that haven't happened yet. Don't use this for subject and overlay data.
- Use timestamp of source for a specific analytic object: Borrow another object's upload schedule instead of this object's upload schedule.
Use special handling for the first upload of the month
If the upload is the first of the month, these options use the last day of the previous month. For any other upload, each falls back to its standard behavior.
- End of previous month (if first load of month) or previous day
- End of previous month (if first load of month) or week
- End of previous month (if first load of month) or use source timestamp
- End of previous month (if first load of month) or current month
- End of previous month (if first load of month) or last specified day of the week
Use special handling near the end of the month
- End of current month (if last day) or previous month: Only counts as current month if the upload literally lands on the last day.
- End of current month (if within 5 business days) or previous month: Counts as current month if the upload is within 5 business days of the last day of the month.
- Later or last specified day of the week or end of previous month: Weekday cutoff, but never earlier than the prior month.