# Opt-Dataset on Data property of a Table **URL:** \ **Category:** Ignition\ **Created:** [February 1, 2017, 4:59pm UTC](https://forum.inductiveautomation.com/t/opt-dataset-on-data-property-of-a-table/12632 "2017-02-01T16:59:10Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![DougSN](https://avatars.discourse-cdn.com/v4/letter/d/a9adbd/32.png) [@DougSN](https://forum.inductiveautomation.com/u/DougSN)\ **Post date:** [February 1, 2017, 4:59pm UTC](https://forum.inductiveautomation.com/t/opt-dataset-on-data-property-of-a-table/12632/1 "2017-02-01T16:59:10Z")
I have a table component which displays some values returned from a stored procedure, based on user-selected parameters. It seems that if the stored procedure returns above a certain amount of rows (seems to be around 10k), the Data property on the table changes from a Dataset to an Opt-Dataset. When this happens, the NULL values returned are coming through as NaN (instead of blank), which displays as a box symbol in the table component, indicating that the ASCII symbol it wants to display cannot be found. When a smaller number of rows is returned, the empty cells display as blank, which is the desired behavior for my application. I couldn’t find any documentation on this feature, is it known? What is an Opt-Dataset? ---
**Author:** ![KathyApplebaum](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kathyapplebaum/32/7261_2.png) [@KathyApplebaum](https://forum.inductiveautomation.com/u/KathyApplebaum)\ **Post date:** [February 1, 2017, 5:32pm UTC](https://forum.inductiveautomation.com/t/opt-dataset-on-data-property-of-a-table/12632/2 "2017-02-01T17:32:11Z")
The OptimizedDataset (which kicks in when the row count \>= 10000) is more efficient for sending the dataset from the gateway to the client. For numeric and date columns, a side effect is that it indeed changes nulls to NaN as you discovered. The box symbol is probably not desired behavior. 😃 I’ll create a bug ticket for that.