Tenant Settings

Tenant settings define information about the tenant, including the data start and end dates.

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.

Example: Rolling start date

Let’s say you have a tenant called Callisto. In the Callisto tenant, you want your data start date to change as time progresses so that old data is not shown in Visier. In this case, you want to hide data from four years ago. To do so, you would navigate to Data > Tenant Settings and apply the following tenant settings:

Start date type: Rolling start date
Start date month offset: 48
End date config type: Auto detect from data

This ensures that Visier loads data starting from 48 months ago based on the most recent date in your latest data transfer.

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. To illustrate each end date config type's behavior, the example columns show what date is available to select if today is June 29, 2017 but the latest upload was April 30, May 2, or June 9.

End date config type	Description	Example 1: Latest upload on April 30	Example 2: Latest upload on May 2	Example 3: Latest upload on June 9
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.	April 30	July 1	June 30
End of current month	Use the end of the month of the latest upload.	April 30	May 31	June 30
End of previous day	Use the end of the latest upload minus one day.	April 29	May 1	June 8
End of previous week	Use the last Sunday of the latest upload.	April 23	April 30	June 4
End of previous month	Use the last day of the previous month of the latest upload.	March 31	April 30	May 31
Use source timestamp	Use the exact time of the latest upload.	April 30	May 2	June 9
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.	March 8	March 8	March 8
Use timestamp of current run	Use the current time.	June 29 (current time)	June 29 (current time)	June 29 (current time)
End of current day	Use the end of the current date.	June 29 (end of day)	June 29 (end of day)	June 29 (end of day)
End of previous month (if first load of month) or previous day	Use the last day of the previous month if it's the first upload of the month. For all other uploads, use the end of the previous day. 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.	April 29 (end of previous day)	April 30 (end of previous month)	June 8 (end of previous day)
End of previous month (if first load of month) or week	Use the last day of the previous month if it's the first upload of the month. For all other uploads, 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.	April 23 (end of previous week)	April 30 (end of previous month)	June 4 (end of previous week)
End of previous month (if first load of month) or use source timestamp	Use the last day of the previous month if it's the first upload of the month. For all other uploads, 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.	April 30 (time of latest upload)	April 30 (end of previous month)	June 9 (time of latest upload)
End of current month (if last day) or previous month	Use the end of the month of the latest upload if it's the last day of the month. If it's any other day of the month, use the last day of the previous month.	April 30 (end of current month)	April 30 (end of previous month)	May 31 (end of previous month)
End of previous month (if first load of month) or current month	Use the last day of the previous month if it's the first upload of the month. For all other uploads, 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.	April 30 (end of current month)	April 30 (end of previous month)	June 30 (end of current 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.	July 1	July 1	July 1
Last specified day of the week	Use the latest week day, as specified, of the latest upload. For example, use the latest Wednesday of the latest upload.	April 26 (latest Wednesday)	April 26 (latest Wednesday)	June 7 (latest Wednesday)
Later or last specified day of the week or end of previous month	Use the latest week day, as specified, of the latest upload without going beyond the previous month. For example, use the latest Wednesday of the latest upload without going beyond the previous month.	April 26 (latest Wednesday)	April 30 (end of previous month)	June 7 (latest Wednesday)
End of current month (if within five business days to end) or previous month	Use the end of the current month of the latest upload if the upload is within five business days of the end of the month. Otherwise, use the last day of the previous month of the latest upload.	April 30 (upload is within 5 days from end of month, use end of current month)	April 30 (upload isn't within 5 days of end of month, use end of previous month)	May 31 (upload isn't within 5 days from end of month, use end of 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 of the latest upload if it's the first upload of the month. Otherwise, use the latest week day, as specified. For example, use the latest Wednesday of the latest upload. 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.	April 26 (latest Wednesday)	April 30 (end of previous month)	June 7 (latest Wednesday)