CSV Interface
Target audience
This document is intended for Demand Driven Technologies Channel Partners, Demand Driven Technologies Implementation Partners and Client Information Technology staff.
This document assumes that the person performing the tasks detailed here is familiar with:
Administration of Windows Server 2016/2019, including IIS
Administration of SQL Server 2016
Editing system configuration files, scripting and command line utilities
Before beginning
This document assumes the following:
The System Administrator has access to a properly prepared instance of Intuiflow
Has correct permissions set up to import into the system
Character Separated Value File Specification
While there are no true column types in the CSV specification the Type column is included to show allowable characters. Be sure to properly escape values which may contain delimiters and text qualifiers. For example, if one of your record values contains your delimiter character, you are required to escape that value. For more information, please reference IETF RFC 4180.
Future versions of Intuiflow may add or reorder columns.
Data Type
Description
Text
Alphanumeric. Full range of numbers, letters and symbols.
Integer
Numeric Only. Any whole number with no decimal places. Culture-specific digit groupings are optional.
Decimal
Any real number with optional minus, decimal and optional digit grouping characters. When the length is specified in the specification below, the format {maxDigits}.{decimalDigits} will be used. For example, “3.2” would mean a maximum up 3 digits with 2 digits after the decimal. (#.##)
Date
The culture-specific representation of Day, Month and Year.
Boolean
True (1) or False (0)
Templates
Empty CSV’s or Templates can be exported via the Intuiflow UI from the Data -> Export menu. Users must be in the Data Exporter Role to access the menu item. Contact your system administrator to be placed in that role if you are not.
UTF-8 Encoding
UTF-8 (UCS Transformation Format—8-bit) is a variable-width encoding that can represent every character in the Unicode character set. It was designed for backward compatibility with ASCII and to avoid the complications of endianness and byte order marks in UTF-16 and UTF-32. To be correctly recognized by R+, CSV files must be UFT-8 encoded and contain the UTF-8 header byte order mark. File may be examined with a text editor like NotePad++ to determine the encoding scheme used and, optionally, to change it.
Naming Conventions
Files may be named anything. For each of the data sets below, the column names in BOLD are identifying fields, and must be present to correctly identify the record type of the CSV file.
Last updated