# Passing Dataset data type to template parameter in Template Canvas?

**URL:** <https://forum.inductiveautomation.com/t/passing-dataset-data-type-to-template-parameter-in-template-canvas/100517>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [January 7, 2025, 3:25am UTC](https://forum.inductiveautomation.com/t/passing-dataset-data-type-to-template-parameter-in-template-canvas/100517 "2025-01-07T03:25:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![aaron1](https://avatars.discourse-cdn.com/v4/letter/a/b5a626/32.png) [@aaron1](https://forum.inductiveautomation.com/u/aaron1)\
**Post date:** [January 7, 2025, 3:25am UTC](https://forum.inductiveautomation.com/t/passing-dataset-data-type-to-template-parameter-in-template-canvas/100517/1 "2025-01-07T03:25:12Z")

</div>

Hi everyone,

Does anyone know if it's possible to pass a dataset to a template parameter in the Template Canvas component?

It's going to be a dataset of just one column with multiple rows. The dataset won't be read from a tag as the dataset will be generated in scripting. But if it can work via a tag then that's fine too.

Have tried a few different syntax but no luck so far...

Many thanks.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/7/97add480bf0ccb12ad988ea00f2dd7b2e2d975c3.png)

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [January 7, 2025, 5:59pm UTC](https://forum.inductiveautomation.com/t/passing-dataset-data-type-to-template-parameter-in-template-canvas/100517/2 "2025-01-07T17:59:28Z")

</div>

The data gets mapped to JSON to be passed into the template, because ultimately the customizer is creating a dataset, and Vision's serialization isn't really happy with datasets-inside-datasets, so we don't let you create them outside of scripting where we basically can't prevent you from doing so.

I would probably recommend a different approach entirely. Maybe the template parameter is just a parameter _name_, and then the template instance uses scripting to retrieve that named parameter from the outer template canvas which gets corresponding custom parameters added to it.