Upload Data Files Using the Solution

Learn how to upload your initial employee data files using the Visier solution.

Introduction

There are multiple ways to load data into Visier, including Visier's data connectors, the Direct Data Intake API, and file upload. The method you choose will be dependent on your specific needs and overall ecosystem.

If your data is stored on a secure file server that only authorized users can access and decrypt or if you prefer to download data from your database, prepare it, and then upload it into Visier, the file upload method is recommended.

Depending on your requirements, Visier offers different options for uploading data files:

• Visier Solution: This option is particularly useful for initial data onboarding, testing, and conducting ad hoc data uploads. For more information, see File Upload Using the Solution.
• Data Upload API: This API allows you to programmatically send data files to Visier. It's a convenient alternative to SFTP. For more information, see Data Upload API.
• Secure File Transfer Protocol (SFTP): Allows you to automate the file upload process by scheduling a data load frequency. This is a great option to use after onboarding your initial dataset into Visier. For more information, see File Upload Using SFTP.

In this tutorial, you will learn how to upload your initial employee data files using the Visier solution.

Objectives

We will first walk you through how to upload your first data files in a new Visier tenant, and then take you through how to generate sources for your data. After sources are created, we will show you how to create and configure mappings for each source. This will connect the source files' columns to the properties in Visier’s analytic objects. We will then show you how to run a job to generate a data version.

By the end of this tutorial, you will have successfully uploaded data files to use in the solution.

In our example, we will be uploading our initial employee data files which includes employee, employee starts, employee exits, and organization hierarchy. This will allow us to analyze employee starts and exits in Visier.

You will learn how to:

• Upload data files using the Visier solution
• Generate sources
• Create and configure mappings to specify how data in your source is loaded into Visier
• Run a job to generate a data version
• Preview the data in the solution

Prerequisites

Before beginning this tutorial, you will need:

• A Visier account that has the following profiles. If you don't have an account, contact your administrator.

  • Data Engineer

• A Visier account with a permission that allows the user to access Guidebooks, analyses, the Explore room, and data access to view the data you’re loading. For more information, see Permission Management.

  • Ad Hoc Analysis

  • Create Analysis Context

  • Change Analysis Context

  • Guidebook

  • View Details

Steps

Prepare data files

To make it easy, we have sample data files that you can load, so you can follow along.

Download the sample data files.

The compressed file includes sample data for employee, employee starts, employee exits, and organization hierarchy:

• employee_tutorial.csv
• employment_start_tutorial.csv
• employee_exit_tutorial.csv
• organization_hierarchy_tutorial.csv

Before we upload our data into Visier, we need to make sure our data files are in the expected format, and follow the recommended file structure and naming conventions. This in an important step as it ensures our files will be successfully uploaded to the solution. To learn more about how to structure your data files, see Data File Guidelines.

Additionally, each data file has specific fields that are required when uploading so we need to ensure we include data for those fields. For example:

The Employee data file needs to include data for the following required fields:

• Snapshot Date

• Employee ID

• Employment Status

The Employee Start data file needs to include the following required fields:

• Event Date

• Employee ID

• Employment Start Type

The Employee Exit data file needs to include the following required fields:

• Event Date

• Employee ID

• Termination Reason

The Organization Hierarchy data file needs to include the following required fields:

• Snapshot Date

• Organization ID

• Parent Organization ID

To learn more about the required and recommended fields for each data file, see Visier Data Dictionaries.

For the purposes of this tutorial, we can skip this step as the sample data files are in the expected format and all required fields are included.

Upload data files in the Visier solution

After our data files have been prepared, the next step is to upload them within Visier’s studio experience, which serves as the administrative design space. To learn more about the studio experience, see Studio Navigation.

After you sign in to Visier, you are directed to the solution experience or the studio experience. This is dependent on capabilities, permissions, and if you’ve previously loaded data into Visier.

1. Sign in to Visier.
2. Do one of the following:
   • If you start in the solution experience, on the navigation bar, click Studio to access the studio experience, and then click Data > Data Transfers.

     

   • If you start in the studio experience, on the global navigation bar, click Data > Data Transfers.

     

3. Compress the data files you want to upload in a ZIP file. You can also upload CSV, XLS, XLSX, and PGP-encrypted files. We can skip this step because the sample data comes as a compressed file. The ZIP file contains data files for employee, employee starts, employee exits, and organization hierarchy.
4. Click Upload File and select the compressed sample data file you downloaded previously. In this tutorial we're uploading the file Tutorial_Essentials_Sample_Data.zip.
5. Click Upload.

   Note: If you upload an XLS or XLSX file containing multiple sheets, each sheet will create a unique data transfer.

   Result: The data files are encrypted and uploaded to a secured file server.

Generate sources

Now that our data files have been uploaded to the solution, we need to generate sources for each file. Sources store data for your solution, for example, Employee data is stored in the Employee source. For more information, see Sources.

Let's start by generating a source for the employee file.

To generate a source:

1. In the Data Transfers tab, hover over the uploaded file.
2. In the Actions column, click the Generate source button .

   Result: A source is created.

Repeat the above steps for the uploaded employee start, employee exit, and organization hierarchy files. In this tutorial, you will generate the following sources:

• employee_tutorial
• employment_start_tutorial
• employee_exit_tutorial
• organization_hierarchy_tutorial

We can check our sources to verify the data was extracted correctly.

1. On the global navigation bar, click Data > Sources.
2. Select a source and click the Uploaded Files tab.
3. Check the latest uploaded file and confirm that the number of records is correct in the Records column. There should only be one file for each source as this is the first time we have loaded this data.

The following table describes the number of records for each file.

Source	File	Number of Records
employee_tutorial	employee_tutorial.csv	10956
employment_start_tutorial	employment_start_tutorial.csv	649
employee_exit_tutorial	employee_exit_tutorial.csv	260
organization_hierarchy_tutorial	organization_hierarchy_tutorial.csv	628

We can also check the Columns tab to ensure all the expected columns have been loaded and that each column has the correct data type. In this tutorial, we want to look at the columns to familiarize ourselves with the sample data.

Create a project

Next, we need to create a project in the studio experience to hold our work. A project is a workspace that allows you to define and edit the solution apart from the current production version of the solution. For more information, see Projects.

1. On the global navigation bar, click Projects.
2. In the Projects room, click New Project.
3. In the New Project dialog, type a name and description for the project. We can name our project Visier Tutorial with a description of Load, configure, and publish essential Employee data.
4. Click Create.

   Result: The project home appears.

Create a data category

Now that we’ve created a project, we need to create a data category for our data.

A data category represents a dataset loaded into Visier that runs on a unique data load frequency. Each data category has its own set of instructions to generate a data version. A data version is a instance of uploaded data with a unique release number. For more information, see Data Versions.

The "instructions" within a data category bring together the mappings from source data to objects in Visier's analytic model.

1. In the project, on the navigation bar, click Data > Data Categories.
2. Click Create Data Category.
3. In the Create data category dialog, type a display name and description. We can name our data category Visier Tutorial Data with a description of Instructions to load data for tutorial.
4. Click Create.

   Result: The data category is created.

After a new data category is created, Visier generates a new tenant setting, Tenant_Design_0, and automatically assigns it to the data category. Tenant settings define information about the tenant, including the data start and end dates. This tenant setting should be automatically assigned to the data category.

Check that the tenant setting is assigned to the data category:

1. In the data category, click the Settings tab.
2. Under Tenant setting, ensure Tenant_Design_0 is selected.

Create mappings

Next, we need to create mappings for each of our sources. Mappings connect the source files' columns to the properties in Visier's analytic objects. For more information, see Mappings.

Let’s start with our employee data and create a mapping for our employee source.

To create a mapping:

1. In the project, on the navigation bar, click Data > Mappings.
2. Click Create Mapping.
3. In the Create mapping dialog, in Data category, select the data category you created. In this tutorial, we named our data category, Visier Tutorial Data.
4. In Mapping type, select the appropriate mapping type. In this tutorial, we will select Regular for all the mappings. For more information about mapping types, see Mappings.
5. Type a display name and a description for the mapping. We can name our mapping Employee Mapping with a description of Data extraction rules for the employee analytic object.
6. Select the source and its corresponding data load target. Because we're starting with our employee data, we will select employee_tutorial as our source and Employee as our data load target. The following table describes which data load target we will be selecting in this tutorial.

   Source	Data Load Target
   employee_tutorial	Employee
   employment_start_tutorial	Employment_Start
   employee_exit_tutorial	Employee_Exit
   organization_hierarchy_tutorial	Organization_Hierarchy

7. In Data type, select the correct data type for the source. In this tutorial, our employee data is Transactional profile. The following table describes which data type we will be selecting in this tutorial.

   Source	Data Type
   employee_tutorial	Transactional profile
   employment_start_tutorial	Conception event
   employee_exit_tutorial	Termination event
   organization_hierarchy_tutorial	Transactional profile

   Note: The data type is dependent on how the source data is formatted. For more information about mapping data types, see Data file types.

8. In Override behavior, select the correct override behavior for the mapping. The override behavior defines how the loader uses newer records to overwrite older records. For more information, see Override behavior. In this tutorial, we will use the default override behavior for each mapping.
9. Click Create.

   Result: The mapping is created.

After we create mappings for the rest of our sources, it's time to configure each mapping.

Configure mappings

Once we have created our mappings, we need to map the source columns to the analytic object properties. This can be done by utilizing the automap feature which streamlines the mapping process through string matching.

Let's start with our employee mapping.

1. In Mappings, select the mapping that you want to configure.

2. In the mapping, click Automap.

   

   Result: The properties with matching source columns are mapped.

3. In Properties, check the mapped items to ensure all your source columns were correctly mapped to a property. A property is mapped correctly if it shows the correct source column name or formula. For example, EmployeeID is mapped to the EmployeeID column and not the Birth_Date column. You can preview the records in the mapping by clicking Preview.

   

Once we're satisfied with our employee mapping, we will have to configure the rest of the mappings to map the source columns to the analytic object properties.

Add business rule

In this tutorial, our employee data is transactional. To correctly use this data in Visier, we need to create a business rule that create profiles from transactions for the Employee subject, which will ensure the headcount is correct when we validate the data.

To add a business rule:

1. In the project, on the navigation bar, click Data > Rules.
2. In the Business Rules tab, click Create Rule.
3. In the Create rule dialog, in Data category, select the data category you created. In this tutorial, we named our data category, Visier Tutorial Data.
4. In Rule type, select Business rule.
5. Type a display name. We can name our business rule Employee Conception and Termination Rule.
6. Select the subject for the business rule. In this tutorial, we are selecting Employee as the subject of the business rule.
7. Type a description. For example, Create profile conceptions and terminations based on events.
8. In Formula, type call call createProfilesForCTEvents(). This generates profile conception and termination events from actual conception and termination events.
9. Click Create.

   Result: The business rule is created.

10. In the business rule we created, in the Configure tab, click Validate.

Run a job to generate a data version

Once we've created and configured our mappings, it's time to run a job from our data category to generate a new data version, this will allow us to preview the data in the solution. Jobs define the tasks needed to load your data into Visier, for more information, see Jobs.

1. In the project, on the navigation bar, click Data > Data Categories.
2. On the data category we created for our data, in the Actions column, click the More button . In this tutorial, we named our data category, Visier Tutorial Data.
3. Click Run job.
4. In the Configure Data Loader dialog, click Run job. In this tutorial, we'll use the default job settings.

To check the status of the job, navigate to Data > Jobs.

• In the Status tab, click Refresh. The job should now appear in the list.

If successful, a release number appears in the Data Version column. This means a data version is generated and the job is complete.

Set the data version

If the data version release behavior is set to manual release or custom release, you will have to change the data version of your project in order to preview the new data version.

To set the data version:

• In a project, on the navigation bar, click Data > Data Categories. For more information, see Set the Data Version.

Check that data is available in the solution

Now that we've generated a data version, we need to confirm that data has been loaded and appears in the solution. At this point, we are not concerned about the accuracy of the values that we see in the solution because we still need to set up the analytic model for the metrics to work correctly. In the next tutorial, we will configure concepts and validate our data.

To preview the solution:

• In the project, on the navigation bar, click Preview Solution.

  Result: A preview version of the solution opens in a new tab.

We will use the Explore room to check that data has been loaded. The Explore room is where you can conduct most of your ad hoc analysis in the solution and customize visuals to suit your needs.

To navigate to the Explore room, click Explore on the navigation bar.

Use the various elements to analyze your data and build a visual to suit your needs.

1. Visual title: Describes and controls the data that is displayed in the chart. Click the Metric picker, Visual picker, and Group By picker in the visual title to change the data that is displayed. For more information, see The Visual Title.
2. Analysis Context toolbar: Change the Analysis Context to select the population and time period for analysis. For more information, see The Analysis Context.
3. Chart: Graphical representation of one or more metric.
4. Side panel: View contextual information about selected metrics and data points, customize the appearance of your chart, and change chart configurations.
5. Visual Actions menu: Use these quick access buttons to perform chart actions and open chart customization and configuration options in the Side panel. For more information, see Visual Actions Menu.

To build a visualization and check data in the Explore room:

1. In the visual title, click the Visual picker and select the Breakdown visual.
2. In the visual title, click the Metric picker and select a metric. In this tutorial, let's select the Headcount metric.
3. In the visual title, click the Group By picker and select an attribute to organize the data. In this tutorial, let's select Organization.
4. Check that the visualization loads and you values appear for your groupings.
5. In the analysis context, click the Time picker. Click to change the granularity, time period, and time window to ensure data has been loaded for the time periods that your source data covers.

If our visualizations load and we see values, then we have successfully loaded data into Visier.

Commit project changes

Now that we’ve confirmed that data has been loaded, it’s a good time to commit our changes. Committing changes acts as a save point for your project.

1. In the project, on the navigation bar, click the Home button .
2. Click the Changes tab in the project home.
3. Click Commit All.
4. In the Commit Changes to Project Revision dialog, type a name and description for the project revision. We can name our revision Initial Data Load with a description of Generated data version.
5. Click Commit now.

Next steps

Now you know how to upload your initial employee data files using the Visier solution. This tutorial walked you through how to upload data files in the Visier solution, generate sources, and map those sources to objects in Visier’s analytic model, as well as how to generate a data version to preview the data in the solution.

After loading data, you will learn how to configure concepts to connect your data values to Visier’s analytic model.

In the next tutorial, you will learn how to configure concepts to connect your data values to Visier’s analytic model. For more information, see Configure Concepts After Loading New Data.