Fields in Vizydrop denote either user-supplied fields or fields within an information schema. There are various types of fields that each represent a different type of data. Fields are also used internally to denote information both required and optional for accounts and filters.
The table below lists the types of fields referred to in the Vizydrop app REST API and in the Vizydrop SDKs. The first column denotes the string name of the type as expected in the API, the second column the type of underlying data, and any comments and remarks for each field type.
||comments and remarks
||a unique identifier for a record; can be either a string or unsigned integer
||UTF-8 encoding, if necessary
||can be decimal, integer, float, or currency
||SDKs validate as either HTTP, HTTPS, or FTP protocols
||may also include time; ISO-8601, can also provide relative times (see Date Spec DSL)
||validates as true/false or 0/1
||allows multiple selections, designed to be used with filter datalists
||allows the user to select a range
||internal type used with accounts and filters to display a help link
||only used in account schemas, rendered as a password input
A Special Note on Dates
Dates, both with and without times, that are parsed as a result of user-input (through the Date Spec DSL) are
timezone-naive objects. Dates received from connected applications may be either aware or naive of timezones and should represent those dates as strings in an ISO-8601 format.
Fields in the SDKs
Fields are represented in different ways in the software development kits provided for creating third-party applications. In the Python SDK, fields are represented as different classes in the