Data Structures

TrackVia uses a View to display data stored in Applications. A View is construct that can have filters, display or hide fields, and read table data. TrackVia uses Roles in combination with Views to restrict read access to data sets. TrackVia uses the Form to enter data into Applications. A Form is a construct that can conditionally show or hide inputs, create and display child records, and set relationships to parents. TrackVia uses Roles in combination with Forms to restrict write access to tables.

Data Type Reference

All single line, email, and link fields are represented as strings of length 255 characters or less. The only difference between them being that email and link fields will validate that the values passed in to them are valid email addresses or URLs.
All paragraph fields are represented as strings of length 65,536 characters or less.
Number, percentage, currency, and auto counters are represented as doubles.
Drop downs are represented by strings of 255 characters or less. To unselect a drop down pass in null.
Checkboxes are represtened by lists of strings of 255 characters or less. To unselect all checkbox choices pass in null.
Both date and date time data types are represented by strings formatted as strings. For input we try to support as many different time formats as possible, but we prefer ISO-8601 format to ensure date and time are always parsed correctly. Note, if the timezone is not specified we will parse times using the timezone of the user. For output we use the ISO-8601 format yyyy-MM-dd'T'HH:mm:ssZ.
Application users are represented by their unique numeric ID.
Parent-child relationships are represented by the unique numeric ID of the parent record stored in the child record. The relationship name is used to reference the relationship. For example, if table Manufacturers has a parent-child relationship with table cars, where each car has a manufacturer, and this relationship is called "car manufacturer" then each car's record will have a field called "car manufacturer" where the value is the numeric ID of a manufacturer.
Documents and images are stored as binary files.
Calculated fields will be represented as the data type that they calculate to. So, a calculated number will be represented as a double and so forth. You will not be able to write to a calculated field.