Perspective UDT drop configuration works to instantiate an embedded view when the instance of that UDT is "single". However, if this UDT is part of a parent UDT (two or more levels), drop config does not work. Ignition does not seem to recognize that the UDT is the same. Is this known? Is there a solution other than just not using nested UDTs (which I have workflow automaticn-based reasons to use)?
I'd suggest this is because the local json for a nested UDT instance doesn't include the typeId key in it, so the designer doesn't realise its a UDT, or what type it is, and hence doesn't show you any options. Seems like a bug to me
I noticed this too, but hoped the intention was a behind the scenes lookup from the parent UDT definition... It does seem like it was intended but is missing.