# UDT Tag History Provider

**URL:** <https://forum.inductiveautomation.com/t/udt-tag-history-provider/22411>\
**Category:** Ignition\
**Created:** [February 7, 2019, 12:17pm UTC](https://forum.inductiveautomation.com/t/udt-tag-history-provider/22411 "2019-02-07T12:17:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![colin.bonner](https://avatars.discourse-cdn.com/v4/letter/c/a87d85/32.png) [@colin.bonner](https://forum.inductiveautomation.com/u/colin.bonner)\
**Post date:** [February 7, 2019, 12:17pm UTC](https://forum.inductiveautomation.com/t/udt-tag-history-provider/22411/1 "2019-02-07T12:17:37Z")

</div>

Would I be correct in the assuming that an instance of UDT cannot use a different Tag History Provider than the one defined in the UDT?

We have lots of different “areas” in the plant that need to log hundreds of tags data to different databases, does this mean I would have to create a duplicate UDT with a different History provider for each database/area?

According to the documentation you can only parameterize a few things on a UDT, seems a bit of a limitation. I ran into something similar with the min/max Engineering limits, as far as I can see you cannot specify different min/max for instances either…

Perhaps I would be better with transaction manager for histroical data? perhaps there is some wizardry I am unaware of, I am pretty new to Ignition.

---

<div class="post-metadata">

**Author:** ![grietveld](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/grietveld/32/6984_2.png) [@grietveld](https://forum.inductiveautomation.com/u/grietveld)\
**Post date:** [February 7, 2019, 3:26pm UTC](https://forum.inductiveautomation.com/t/udt-tag-history-provider/22411/2 "2019-02-07T15:26:11Z")

</div>

There is an override button next to the History Provider on each instance. If you want an instance of the UDT to use a different provider, you can click the button next to those settings to override it to another provider.

This should allow you to change the provider with still using the same DataType and most of the settings.

---

<div class="post-metadata">

**Author:** ![colin.bonner](https://avatars.discourse-cdn.com/v4/letter/c/a87d85/32.png) [@colin.bonner](https://forum.inductiveautomation.com/u/colin.bonner)\
**Post date:** [February 7, 2019, 3:33pm UTC](https://forum.inductiveautomation.com/t/udt-tag-history-provider/22411/3 "2019-02-07T15:33:16Z")

</div>

Oh my god, I completley missed that. Thanks! In my defense it’s a pretty inconspicuous button to say the least.

---

<div class="post-metadata">

**Author:** ![grietveld](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/grietveld/32/6984_2.png) [@grietveld](https://forum.inductiveautomation.com/u/grietveld)\
**Post date:** [February 7, 2019, 3:36pm UTC](https://forum.inductiveautomation.com/t/udt-tag-history-provider/22411/4 "2019-02-07T15:36:13Z")

</div>

No worries. I agree, it doesn’t really specify what it does outside of training, and otherwise have to be brave enough to push the random button haha
