Data Tables store a set of data values that conform to a Table Structure. The table is set up so that each row of the table contains one unique set of Index values, followed by the set of data values that correspond to that unique index.
You can have multiple Data Tables associated with a table structure. You will select which of the existing data tables you want to use for a referenced data table structure when you create and run your projection. This enables you to re-run the same projection with different assumptions by selecting a different data table.
Here is an example of a Commission Rate Table:
And this is the Table Structure for that table which designates the columns and column types:
To set up a table, you will first create or select a table structure you wish to use. You can learn more about Table Structures here.
Slope’s table editor allows you to add and edit up to 100,000 rows of data within the interface. You can use the right click menu and common keystrokes to select, cut, copy and paste data as well as undo and redo a change.
To insert a row, use the right click menu. Additionally, you can copy and insert multiple rows with or without data.
Creating a Data Table Default Index
Empty index values are treated as a default. Clearing out the value in an index field will display the <DEFAULT> label. When referenced index values match those specified in the index columns, the values in the data columns will be used. When the referenced index values don’t match those specified in the index columns, the values in data columns corresponding to the default index values will be used. This allows you to define a standard value or set of values in a data column using <DEFAULT> and then define specific exceptions.
An example of a table using default values is below. The specifics of the example below are explained from most specific to least specific.
- If you pass in a Plan Code of PC25 and the year is 2019, the Commission Rate will be .030.
- if you are passing in a Plan Code of PC1 or PC9 and any year, a commission rate of .100 will be applied.
- If you pass in PC25 and an Issue Year not between 2018 and 2021 , the default Commission Rate of .050 will be applied.
- If you passed in an Issue Year of 2021 and any plan code, a .028 Commission Rate will be applied.
- A default commission rate of .05 will be applied unless the plan code and issue year combination matches one of the other combinations of values in the index columns.
Defaults can be used for both Exact Match and Range Lower bound lookup types.
Using Drop Down List column types to restrict data table values
Drop down list columns offer the user a list of possible values for a column and will provide a warning when a value does not match the options. Using this data type can help prevent and identify data errors.
The list of values for your data table column is defined using a Static Array.
Once the static array is created with the possible values you can create your Drop Down List column. On the Table Structure screen either add or edit your column and select "Drop Down List" for Data Type and then select the array you created which has the possible values.
Once in the table editor, you will see the array values show as options in the column configured as a Drop Down List.
Entering a value that does not match the options defined in the Array will display a warning to alert the user that the value does not match one of the values defined in the array.
Note that all data columns set to a data type of "Drop Down List" are treated like string values in a projection.
Large Data Tables
For tables with more than 100,000 records, you will need to import them and select the File Only checkbox. This is done by clicking the import icon in the top right corner of the table editor, selecting “Add New File”, selecting the file location, providing a name and checking the “File Only” checkbox. It is important to note that validation on these tables is handled at runtime as the data is not stored in-memory.
Frequently Asked Questions:
When is a new data table version created?
When a data table is run in a projection and then edited (post-run), those edits will be saved as a new version of the table. The projection that has been run, will remain linked to the historical version of the table so that you can always look back at the state of the assumptions at the time it was run.