# Data set on a Template

**URL:** <https://forum.inductiveautomation.com/t/data-set-on-a-template/25819>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [June 13, 2019, 10:56pm UTC](https://forum.inductiveautomation.com/t/data-set-on-a-template/25819 "2019-06-13T22:56:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![tyrel.parker](https://avatars.discourse-cdn.com/v4/letter/t/47e85d/32.png) [@tyrel.parker](https://forum.inductiveautomation.com/u/tyrel.parker)\
**Post date:** [June 13, 2019, 10:56pm UTC](https://forum.inductiveautomation.com/t/data-set-on-a-template/25819/1 "2019-06-13T22:56:56Z")

</div>

I built a template that has a data set property on it, and everything was working great until I needed to add a new column to the template data set and that column did not propagate to all of the instances of the template. Is there a way to fix this?

---

<div class="post-metadata">

**Author:** ![bvaldovinos](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bvaldovinos/32/6315_2.png) [@bvaldovinos](https://forum.inductiveautomation.com/u/bvaldovinos)\
**Post date:** [June 14, 2019, 7:31pm UTC](https://forum.inductiveautomation.com/t/data-set-on-a-template/25819/2 "2019-06-14T19:31:57Z")

</div>

If you added the new column to your dataset on the original template, and not an instantiation of that template, this should propagate correctly. I would double check that you edited the template definition.

Where is your template created? _Global \< Templates_? Or _Project \< Templates_?

---

<div class="post-metadata">

**Author:** ![tyrel.parker](https://avatars.discourse-cdn.com/v4/letter/t/47e85d/32.png) [@tyrel.parker](https://forum.inductiveautomation.com/u/tyrel.parker)\
**Post date:** [June 14, 2019, 7:34pm UTC](https://forum.inductiveautomation.com/t/data-set-on-a-template/25819/3 "2019-06-14T19:34:55Z")

</div>

8.0 doesn’t have global templates, but I did verify that I made the change to the actual template and not an instantiation of the template.

---

<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:** [June 14, 2019, 7:48pm UTC](https://forum.inductiveautomation.com/t/data-set-on-a-template/25819/4 "2019-06-14T19:48:57Z")

</div>

This isn’t a great workaround, but for the sake of clarification - if you delete the existing _instance_ of the template and create a new one, I assume it gets the correct value for the dataset?

We probably aren’t “diffing” the actual dataset in the template master (in part, because we expect them to be overriden) and also in part because diffing datasets is expensive. If you can confirm the behavior on a _new_ template instance, I’d say it’s “working as intended”, although a case could be made for changing that behavior ([ideas.inductiveautomation.com](http://ideas.inductiveautomation.com) 🙂 )

---

<div class="post-metadata">

**Author:** ![tyrel.parker](https://avatars.discourse-cdn.com/v4/letter/t/47e85d/32.png) [@tyrel.parker](https://forum.inductiveautomation.com/u/tyrel.parker)\
**Post date:** [June 14, 2019, 8:58pm UTC](https://forum.inductiveautomation.com/t/data-set-on-a-template/25819/5 "2019-06-14T20:58:59Z")

</div>

That is correct. New instances of the template will have the dataset from the template. If that is the way it is supposed to work then I’ll probably just use a bunch of properties rather than a dataset of properties since those will propagate down to the instances of the template.