# \[IGN-8148\]Is it possible to use a whole tag as a custom property / drop target for a template, or to reference the source tag of a non-UDT drop target?

**URL:** <https://forum.inductiveautomation.com/t/ign-8148-is-it-possible-to-use-a-whole-tag-as-a-custom-property-drop-target-for-a-template-or-to-reference-the-source-tag-of-a-non-udt-drop-target/74203>\
**Category:** Ignition\
**Tags:** vision, ignition81\
**Created:** [May 26, 2023, 12:08am UTC](https://forum.inductiveautomation.com/t/ign-8148-is-it-possible-to-use-a-whole-tag-as-a-custom-property-drop-target-for-a-template-or-to-reference-the-source-tag-of-a-non-udt-drop-target/74203 "2023-05-26T00:08:24Z")\
**Posts on this page:** 9\
**Page:** 3

<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:** [June 3, 2023, 11:23am UTC](https://forum.inductiveautomation.com/t/ign-8148-is-it-possible-to-use-a-whole-tag-as-a-custom-property-drop-target-for-a-template-or-to-reference-the-source-tag-of-a-non-udt-drop-target/74203/41 "2023-06-03T11:23:43Z")

</div>

Tag Paths already have an underlying, structured java object. That is entirely orthogonal to the rename behavior you desire.

---

<div class="post-metadata">

**Author:** ![sherman](https://avatars.discourse-cdn.com/v4/letter/s/e5b9ba/32.png) [@sherman](https://forum.inductiveautomation.com/u/sherman)\
**Post date:** [June 3, 2023, 9:22pm UTC](https://forum.inductiveautomation.com/t/ign-8148-is-it-possible-to-use-a-whole-tag-as-a-custom-property-drop-target-for-a-template-or-to-reference-the-source-tag-of-a-non-udt-drop-target/74203/42 "2023-06-03T21:22:23Z")

</div>

Why would it be orthogonal? If they have object references their printed path should just be a property, and then updating it in the tag browser should be able to update it everywhere it is referenced -- that doesn't seem to currently be the case though

---

<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:** [June 4, 2023, 1:06am UTC](https://forum.inductiveautomation.com/t/ign-8148-is-it-possible-to-use-a-whole-tag-as-a-custom-property-drop-target-for-a-template-or-to-reference-the-source-tag-of-a-non-udt-drop-target/74203/43 "2023-06-04T01:06:30Z")

</div>

Object references are constructed from configuration. Changing the references doesn't propagate to config.

---

<div class="post-metadata">

**Author:** ![sherman](https://avatars.discourse-cdn.com/v4/letter/s/e5b9ba/32.png) [@sherman](https://forum.inductiveautomation.com/u/sherman)\
**Post date:** [June 4, 2023, 11:43pm UTC](https://forum.inductiveautomation.com/t/ign-8148-is-it-possible-to-use-a-whole-tag-as-a-custom-property-drop-target-for-a-template-or-to-reference-the-source-tag-of-a-non-udt-drop-target/74203/44 "2023-06-04T23:43:24Z")

</div>

Ah it would need a config propagation as well

---

<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:** [June 5, 2023, 12:09am UTC](https://forum.inductiveautomation.com/t/ign-8148-is-it-possible-to-use-a-whole-tag-as-a-custom-property-drop-target-for-a-template-or-to-reference-the-source-tag-of-a-non-udt-drop-target/74203/45 "2023-06-05T00:09:50Z")

</div>

Actually, even more than that. Altering objects and references, even if there wasn't configuration to worry about, still wouldn't suffice. Because for most of Ignition, the objects are not just one instance in one place, but instances in each of many separate processes, typically not even in the same physical hardware. So, in the real environment, alterations not only have to propagate back to the startup configuration, but also to all other instances.

---

<div class="post-metadata">

**Author:** ![sherman](https://avatars.discourse-cdn.com/v4/letter/s/e5b9ba/32.png) [@sherman](https://forum.inductiveautomation.com/u/sherman)\
**Post date:** [June 5, 2023, 9:34pm UTC](https://forum.inductiveautomation.com/t/ign-8148-is-it-possible-to-use-a-whole-tag-as-a-custom-property-drop-target-for-a-template-or-to-reference-the-source-tag-of-a-non-udt-drop-target/74203/46 "2023-06-05T21:34:02Z")

</div>

It would definitely need to be an active function to push changes to everything, which is why I guess it doesn't exist.

It would be a supremely valuable functionality for development and maintenance, though.

---

<div class="post-metadata">

**Author:** ![woodsb02](https://avatars.discourse-cdn.com/v4/letter/w/6a8cbe/32.png) [@woodsb02](https://forum.inductiveautomation.com/u/woodsb02)\
**Post date:** [June 25, 2023, 2:03am UTC](https://forum.inductiveautomation.com/t/ign-8148-is-it-possible-to-use-a-whole-tag-as-a-custom-property-drop-target-for-a-template-or-to-reference-the-source-tag-of-a-non-udt-drop-target/74203/47 "2023-06-25T02:03:46Z")

</div>

I just wanted to say this has been an educational read. I suspect almost everyone getting started with Ignition will come across this debate at some point.

I feel like there should be a “best practices” section of the documentation that explains the options of UDT vs tag paths, and when it is best to use them.

Specifically - my take away from this thread was:

- UDTs for structured data, but don’t bind to templates/views
- tagPaths for passing to templates/views - with dropconfig tagPath support only available in perspective (currently)

---

<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:** [June 25, 2023, 11:52am UTC](https://forum.inductiveautomation.com/t/ign-8148-is-it-possible-to-use-a-whole-tag-as-a-custom-property-drop-target-for-a-template-or-to-reference-the-source-tag-of-a-non-udt-drop-target/74203/48 "2023-06-25T11:52:40Z")

</div>

> [@woodsb02](#):
>
> a “best practices” section of the documentation

Part of the reason for topics like this is that IA prominently features UDT binding in its training. Which produces a bias towards poor practices that a user has to unlearn to make headway in more advanced and efficient methods.

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [June 25, 2023, 10:14pm UTC](https://forum.inductiveautomation.com/t/ign-8148-is-it-possible-to-use-a-whole-tag-as-a-custom-property-drop-target-for-a-template-or-to-reference-the-source-tag-of-a-non-udt-drop-target/74203/49 "2023-06-25T22:14:45Z")

</div>

Best practices sometimes conflict with marketing material 🙄

[Previous page](https://forum.inductiveautomation.com/t/ign-8148-is-it-possible-to-use-a-whole-tag-as-a-custom-property-drop-target-for-a-template-or-to-reference-the-source-tag-of-a-non-udt-drop-target/74203.md?page=2)
