# How can you display a script dataset in a Perspective Table?

**URL:** <https://forum.inductiveautomation.com/t/how-can-you-display-a-script-dataset-in-a-perspective-table/81492>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [November 4, 2023, 12:34am UTC](https://forum.inductiveautomation.com/t/how-can-you-display-a-script-dataset-in-a-perspective-table/81492 "2023-11-04T00:34:36Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [November 4, 2023, 1:22pm UTC](https://forum.inductiveautomation.com/t/how-can-you-display-a-script-dataset-in-a-perspective-table/81492/11 "2023-11-04T13:22:02Z")

</div>

Datasets, themselves, allow just about anything as a column type. But that freedom creates huge problems for Ignition's infrastructure when arbitrary datatypes are stored in tags. So the tag machinery of Ignition checks the columns types of any incoming dataset against a whitelist, and rejects any dataset that doesn't conform.

You have a couple options:

- convert the troublesome columns to some other datatype (stringification is common, if you don't need the functionality of the object's true type), or

- store the dataset in memory, typically in a top-level script library variable, and have your uses look for it there. (You might find my `globalVarMap()` functions in my [Integration Toolkit](https://forum.inductiveautomation.com/t/automation-professionals-integration-toolkit-module/74934) module helpful.)

---

_[View the full topic](https://forum.inductiveautomation.com/t/how-can-you-display-a-script-dataset-in-a-perspective-table/81492)._