While Data Stores are the primary data repositories of a Solution, Tables are primarily used as utilities and for storing configuration data for business rules.
Like Data Stores, Tables are materialized as SQL Server tables and can be read and written to by any SQL script or process having the required permissions. Data is stored "as is", so you do not need to use an InVision API to read or write data to a Table. This makes it easy to integrate with other tools, such as Excel or a custom Web Service, to export and import data to and from InVision.
See how to create a table, configure the table schema in the video section here.
Unlike Data Stores, Tables do not have data sources and you cannot apply foreign key constraints to Tables.
To enable features such as Periodic Input, Rollover, and Transaction Pipeline Processing, you need to set up the Time Frame configuration for a Setting. The Time Frame is the feature that all date-related information for Settings and Data Stores are derived from, which makes it a very important part of most InVision solutions. Read more about the Time Frame feature here.
Cell Adapter Ruleset
The Ruleset configuration for the Transaction Pipeline Cell Adapter component. Read about the required configuration here.
The Ruleset configuration for the Transaction Pipeline Distributer component. Read about the required configuration here.
The Ruleset configuration for the Transaction Pipeline Spawner component. Read about the required configuration here.
InVision provides a way to hook into the process of saving Worksheets and Setting data from the end-user client. The hook lets you execute custom business logic such as data validation, modifying data, sending messages, and so on. Read more about the On Save feature here.