Additional Import Data field headers

If you have the Power add-on you will have the ability to import data fields via a properly formatted csv file.  All columns MUST have a header row with the  field name. All fields are short text fields, up to 255 characters, unless otherwise noted.  The header text is NOT case sensitive.

If you are using the category (aka tagalong) functionality of Power you may want to import and assign a category slug on the fly.  The header field name is:

category (or plural categories).

If you wish to import and assign more than one category  per location , you will need to use a comma-separated list for the data field  (category).  Example: My location has more than one category associated with it, I want to indicate it is a hotel,restaurant, and has music.  Category  for that location would show under the column with the header row “category”…. hotel,restaurant,music

Alternatively, to define parent/child relationships , i.e.  hierarchical categories , use a double colon as the separator Example the Parent is Facility, the child is showroom.

Facility::Showroom.

Example CSV Import Files

People often ask for examples of CSV import files. Here are some examples you can use as a model for your own imports.   You will need the Power add-on to import locations.

Example of what your Excel or Google Sheets with CORRECT SL_FIELD NAMES in the header rows would look like:
Continue reading “Example CSV Import Files”

Location Imports With Power Add On

The location imports have been updated with the Power add on in order to simplify and speed up the import process.  The CSV file format remains as the preferred import method for locations.

CSV File Format

The CSV file should be a UTF-8 encoded file with proper quotes around strings and commas between fields.

Special characters should be stripped or converted to proper UTF-8 format.   In our experience many applications such as Numbers and Excel will not strip special characters properly during a UTF-8 CSV file export.   Google Sheets has been a good application for importing those CSV files and re-exporting them with special characters removed.

The CSV file must have a header row defining field names as the first row of the file.   All other rows must contain proper CSV data.      Rows cannot contain more columns (fields) that defined by the header row.    That is often an indicator that special characters exist in your file and is used as a safety stop mechanism in the import processor.

CSV File Headers

All location import files must start with a field name header.   This is the first line of the CSV file that contains the name of each locator field at the top of the column.    The option to “not include a  header + is no longer optional in the Power add-on.

Header field names are not case sensitive.    The field names will be stripped of any character that is not a letter, number, hyphen, or underscore.    If it makes your file more readable you can use a name such as “Address 2” which will be changed to “address2” , then the file is processed.    Keep in mind the “sanitized key” version of whatever you use as the header MUST match the list of field names below.
Continue reading “Location Imports With Power Add On”