Skip to main content

Set up your import files

Prepare import workbooks, headers and field values, and distinguish account email, organization Code and record ID matching.

Prepare the file for the object you intend to import, then check its format, headers and matching values before uploading. This guide covers:

  1. Requirements for all import files

  2. Association between object types and property values

Once you have set them up, you may learn how to:


Requirements for all import files

Import files for each object type require their own properties.

  • Use an .xlsx or .xls Excel workbook containing only one worksheet. For data-list imports, check the uploader for any CSV option described in the data-list import guide; use that entry’s supported formats.

  • The import file should contain fewer than 10,000 objects/rows and is smaller than 5MB.

  • Include a header row in your file.

    • Each header name should be unique.

    • Each column header should correspond to a property that exists for the object type being imported.

    • During the import process, Yeeflow will match the column header to the property name to be updated. Otherwise, you can manually map your column headers to property values.

  • Include the matching value required by the object you are importing. For example:

    • For user imports, map the account email-address column to Login Account.

    • For department or location imports, provide the required unique Code.

    • For data-list updates, provide the target list record’s item ID in each row that should update an existing record.

  • Keep values under the columns mapped to the intended properties. For example, put account email addresses in the column mapped to Login Account and department codes in the column mapped to Department.

  • Where the import matching requirements are met, the documented process uses the first matching row to add the record and later matching rows to update it. Review duplicate rows before importing so the intended values are clear.


Association between object types and property values

During the import, Yeeflow will reference system field name and match the objects in each file by the column header name. The matched objects will be associated.

For multi-value updates, separate the supplied values as described below. Test a representative existing record to check whether your import entry replaces or combines its previous values before processing the full file.

Please follow below requirements for each object type.

Common Fields/Objects

Field/Object Type

Requirements

Text Box
Text Area

The string used for [Text Box]association must be under 200 characters.
And for [Text Area] association must be under 5000 characters.

Number

Must be a number formatted value.

Currency

Must be a number formatted value, with non-symbol.

Dropdown
Radio Button

Must have the same value in the existing list of each object and be case-sensitive.

Checkbox

For a multiple checkboxes property in an import, separate its values with commas (e.g. value 1,value 2,value 3).

Date Picker

Must be a date or datetime formatted value.
You need to select the "Time zone" and the import will directly convert the date(datetime) in the file to the time zone displayed in Yeeflow system settings.

Time Picker

Must be a time formatted value.

You need to select the "Time zone" and the import will directly convert the time in the file to the time zone displayed in Yeeflow system settings.

Switch

TRUE displays as ON, Yes or checked in Yeeflow.

FALSE displays as OFF, No or unchecked in Yeeflow.

Hyperlink

Must be a complete URL which starts with an "HTTPS://" or "HTTP://" prefix.

Associated Fields/Objects

Field/Object Type

Requirements

User /multiple users

Must have a data with account email address. (e.g. [email protected]) and the account should be active user(s) in your Yeeflow User management.

For a multiple user property in an import, separate its values with commas (e.g. [email protected],[email protected]).

A multiple user must be under 20 email addresses.

Department/multiple Departments

Must have a data with the same value(s) in Yeeflow Department Codes and be case-sensitive.

For a multiple Department property in an import, separate its values with commas (e.g. A,B,C1).

A multiple Department must be under its set of "Max Selection".

Get the Department Code from the Departments management page. Preserve the complete code, including leading zeros.

Location

Must have a data with the same value(s) in Yeeflow Location Codes and be case-sensitive.

Get your Yeeflow Location Codes from Location page.

Cost Center

Must have a data with the same value(s) in Yeeflow Cost Center Codes and be case-sensitive.

For a multiple Cost Center property in an import, separate its values with commas (e.g. CC1,Dd).

A multiple cost center must be under its set of "Max Selection".

Get your Yeeflow Cost Center code from its page.

Metadata/Multiple metadata

Must have a data with the same value(s) in selected Metadata Codes and be case-sensitive.

For a multiple metadata property in an import, separate its values with commas (e.g. T1,T2).

A multiple metadata must be under its set of "Max Selection".

Get your metadata codes from its page.

Lookup

Lookup object offers the lookup itemId(identifier) or other indexed field for matching import.

Must have a data with the same value(s) in associated lookup list and be case-sensitive.

For a multiple lookup property in an import, separate its values with commas (e.g. Value 1,Value 2; or e.g. itemId 1,itemId 2).

A multiple lookup must be under its set of "Max Selection".

During your import process, ensure that associated list field(s) be matched correctly. E.g. Id column should map to Id field; Number column should map to number property field.

Note: Only indexed field in associated lookup list can be referenced in the corresponding drop-down menu.

Historical Department Code column with values including 01-01 and 01-02.

This crop shows the Department Code column in an original English help-center image. Its capture date and product build are unknown; use the codes in your own organization when preparing a file.

Not supported Fields/Objects

  • Calculated - can be auto-calculated when import

  • Rich Text

  • Attachment

  • Image

  • Tag

Did this answer your question?