# \[BUG-1461\] Changing nested UDT Parent Type not working in instance **URL:** \ **Category:** Ignition\ **Tags:** ignition80\ **Created:** [March 3, 2020, 5:09am UTC](https://forum.inductiveautomation.com/t/bug-1461-changing-nested-udt-parent-type-not-working-in-instance/32754 "2020-03-03T05:09:32Z")\ **Posts on this page:** 10\ **Page:** 1
**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:** [March 3, 2020, 5:09am UTC](https://forum.inductiveautomation.com/t/bug-1461-changing-nested-udt-parent-type-not-working-in-instance/32754/1 "2020-03-03T05:09:32Z")
v8.0.8 I have a UDT that has a UDT instance nested within it that I want to be configurable at the parent UDT’s instance level. For example, in the screenshot below, `Interface Test` is an instance of `PLC Itnerface 1`, and I want to change the nested UDT instance within it, called `Payload`, from it’s original `Bay` UDTType to `Location`. I have done this in the screenshot and applied it, but you can see that the tags under it do not reflect the tags within the `Location` UDT definition. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/e/e5f52441069a3b48d7e7db6737f4c4c3d4fae707.jpeg) I also end up getting these warning signs beside the tags (which belong to the `Bay` UDTType, and not to the new `Location` UDTType) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/e/e632f2f69509de4cbf8eafaae1e7a23d01629020.png) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/0/074b6b6b6364ab8dd18367710cd14a54564243de.png) ---
**Author:** ![jespinmartin1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jespinmartin1/32/57175_2.png) [@jespinmartin1](https://forum.inductiveautomation.com/u/jespinmartin1)\ **Post date:** [March 3, 2020, 5:23am UTC](https://forum.inductiveautomation.com/t/bug-1461-changing-nested-udt-parent-type-not-working-in-instance/32754/2 "2020-03-03T05:23:31Z")
Can you decribe where Payload\>Height Length and Width, come from. Is it from Bay Data Tye? ---
**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:** [March 3, 2020, 5:24am UTC](https://forum.inductiveautomation.com/t/bug-1461-changing-nested-udt-parent-type-not-working-in-instance/32754/3 "2020-03-03T05:24:47Z")
> [@jespinmartin1](#): > > Can you decribe where Payload\>Height Length and Width Correct, these come from the original `Bay` data type ---
**Author:** ![jespinmartin1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jespinmartin1/32/57175_2.png) [@jespinmartin1](https://forum.inductiveautomation.com/u/jespinmartin1)\ **Post date:** [March 3, 2020, 5:55am UTC](https://forum.inductiveautomation.com/t/bug-1461-changing-nested-udt-parent-type-not-working-in-instance/32754/4 "2020-03-03T05:55:38Z")
What you’re to do is not conventional. Making a change of a parent data type inside a UDT instance with nested data types. I advice to create in the data type, in your case, two nested data types with it parent variation. And when creating the UDT instance just disable the one you don’t need. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/0/088c4756856480daaaa0996f4e09928daf608eb0.png) and then ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/5/55a935fb0390e9d08c64441cd2dfa0bae989772a.png) ---
**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:** [March 3, 2020, 6:00am UTC](https://forum.inductiveautomation.com/t/bug-1461-changing-nested-udt-parent-type-not-working-in-instance/32754/5 "2020-03-03T06:00:37Z")
It may not be conventional, but the facility to do it is certainly made available, as any (most?) properties of a UDT are property overridable, including the Parent Type. So this, in my opinion, is most certainly a bug in behaviour. It’s also a very common way to use templates within another SCADA application (not that features of different SCADA packages are necessarily interchangeable). ---
**Author:** ![bmusson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmusson/32/87530_2.png) [@bmusson](https://forum.inductiveautomation.com/u/bmusson)\ **Post date:** [January 5, 2021, 11:57pm UTC](https://forum.inductiveautomation.com/t/bug-1461-changing-nested-udt-parent-type-not-working-in-instance/32754/6 "2021-01-05T23:57:05Z")
@nminchin did you ever find a solution for this? I’m running into a similar situation where I’d really like to be able to change the parent type of a nested UDT. The green “override” icon updates as if the change was accepted, but the child UDT doesn’t change type. I’m on 8.1.2 nightly (20210105-0209). ---
**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:** [January 6, 2021, 12:12am UTC](https://forum.inductiveautomation.com/t/bug-1461-changing-nested-udt-parent-type-not-working-in-instance/32754/7 "2021-01-06T00:12:00Z")
Nope, never heard anything from IA about it. It wasn’t actually for my project but for a colleague’s. I think he probably went with the method Jonathan mentioned. ---
**Author:** ![chi](https://avatars.discourse-cdn.com/v4/letter/c/0ea827/32.png) [@chi](https://forum.inductiveautomation.com/u/chi)\ **Post date:** [January 8, 2021, 2:13pm UTC](https://forum.inductiveautomation.com/t/bug-1461-changing-nested-udt-parent-type-not-working-in-instance/32754/8 "2021-01-08T14:13:04Z")
I just found your post after i spent a couple of hours on this problem. I have a comples UDT defined with a default nested type and want to change the nested type to a specific implementation depending on the connected plc type. Maybe a developer can at least tell if this a bug or a misunderstood feature. ---
**Author:** ![bmusson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmusson/32/87530_2.png) [@bmusson](https://forum.inductiveautomation.com/u/bmusson)\ **Post date:** [January 8, 2021, 4:09pm UTC](https://forum.inductiveautomation.com/t/bug-1461-changing-nested-udt-parent-type-not-working-in-instance/32754/9 "2021-01-08T16:09:25Z")
> [@chi](#): > > I have a comples UDT defined with a default nested type and want to change the nested type to a specific implementation depending on the connected plc type. That’s exactly what I’m trying to accomplish too. > [@chi](#): > > Maybe a developer can at least tell if this a bug or a misunderstood feature. I agree, if this override is not meant to work then the UI should probably be updated to remove the option. ---
**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 8, 2021, 4:49pm UTC](https://forum.inductiveautomation.com/t/bug-1461-changing-nested-udt-parent-type-not-working-in-instance/32754/10 "2021-01-08T16:49:45Z")
Looks like this is under development, and the resolution is to disallow changing the UDT parent type from an instance, for what it’s worth.