Add File Sets to a Job
Learn how to add file sets to a job.
File sets define the expected numbers of files per source. By adding file sets to your data version job, you enable an additional level of validation support to your data loads.
For example, if you configure the file set validation to expect placement events, hire events, and turnover events, but only send one of those files, the job will fail file validation due to missing files. This provides more confidence that the data version contains a complete data load.
Note: If Visier receives files that don’t align with the job’s file set validation, the data load will fail. You can investigate load failures by opening a project and navigating to Validation > Debugging > File Validation.
The following screenshot shows the file sets interface in Visier, found in a project at Data > Data Categories.
- File set. The collection of sources and their expected number of files.
- Source. A source in the job that you can set an expected number of files.
- Definition of expected files number. Whether the expected number of files is an exact number, range, minimum number, or maximum number.
- Number of files. The number of files that Visier expects to receive for the source.
- Source Optional? toggle. Whether or not the source is optional for data loads. If the source is optional, the data load may still succeed if new data for this source is missing.
Create a new file set for a job
- Open a project.
- Navigate to Data > Data Categories.
- On the job that you want to add file set validation, click the More button > Edit > File Sets Validation.
- Click Add Fileset.
- Type a name and description.
- Click Save.
Result: A new file set is created and pre-populated with the available mapped sources for the job.
Note: Validity start date and validity end date are legacy features that are no longer required for file set validation.
- Define the file set by doing the following:
- Select whether the file set is an Exact number, Range, Min, or Max. The default is an exact number based on the files used in the current production version.
Tip: If your tenant is not auto-releasing data versions, such as if you have daily data loads but do not publish data versions to production daily, Visier may double count files. Use a minimum count to avoid double counting.
- Type a number or range of numbers for each source to define the expected files to receive for that source.
- Optional: Make the source optional by enabling the Source Optional? toggle.
- Select whether the file set is an Exact number, Range, Min, or Max. The default is an exact number based on the files used in the current production version.
- When finished, click Save.
Note: If a data transfer fails file validation, administrators will receive an email notification describing the failure reason.