Using the Generic Flat File Source

Importing the Flat File

1. In the Import Accounts tab, select Import.

2. Select the template-formatted file, and then select Open. Information about the file is loaded into the Current File section. You will see a success status after a successful import.

   Note
   You might see an error message if your flat file does not match the template required for the source you are editing. For more information, refer to Source Status Messages.

3. Your next steps depend on how your org is currently configured:

   • To create identities based on the account information from this source, you must create an identity profile for the source.
   • If you already have identities in the system, go to Identities > Identities List and select a user to verify that their account from the source appears as expected. For more information on the identities list, refer to Managing Identities.

Note
You can also export your current account data, edit it, and upload it again using the steps described above. For more information on exporting your data, refer to Sharing and Exporting Data, Visualizations, and Dashboards.

File Structure

In the file each row represents one account (with exception of multi-valued values). Each column has the ability to hold values of data that are associated with the account and are of a certain fixed order. These columns should be in the same order as the Account Schema. Their data can be "left blank" as long as the fields are not required. The file should be sorted based on the Account ID attribute. This is especially important for handling multi-valued attributes.

The first row of the file is the header of the file, and will not be read.

Example:

id	name	givenName	familyName	...	This header row will be skipped
1	jdoe	John	Doe	...	This is the first account
2	msmith	Mary	Smith	...	This is the second account

Handling Multi-Valued Attributes

Some attributes, like groups, support the ability to have multiple values, and are stored as a list. In order to model this, you will put each value on a separate row for that field. All additional values should be repeated.

Example:

id	name	...	groups	...	This header row will be skipped
1	jdoe	...	Admins	...	This is the first account
2	jdoe	...	Employee	...	This is a continuation of the first account. Notice how values repeat, except for the multi-valued column
3	msmith	...	Employee	...	This is the second account

Note
The name is a single-valued attribute.

This will yield 'jdoe' with Admins and Employee groups, and 'msmith' with a single Employee group.

Account Status

For the Flat File source, to set an account as enabled or disabled based on the values inside a specific column, you can add the IIQDisabled (string) attribute in the source account schema. For more information on editing the account schema, refer to Managing Source Account Schemas.

The following SQL query can be used to set up the state for the account:

select ... case when Active=1 then 'false' else 'true' end as IIQDisabled from ...