You can't link a control, indicator, or constant to a typedef. You either have to customize the control, or create a control, indicator, or typedef from an existing typedef on the diagram. Even if you could, doing it from a value property mode is going even farther out on a limb.
Thanks for the clarification. Something doesn't seem logical about it not being a typedef. So I'll kudo the idea. But it might have some logical answer based on the datatypes and whether they are strict or non-strict or something like that. And that trying to make the creation of the control/indicator/constant a typedef would break some other part of LabVIEW's underlying code in how it deals with typedef's and property nodes.
This seems like a bug, since if you create it from the control itself, it is linked to the typedef. I think you should report this for a CAR, not a new feature idea.
I did CAR it... #192142. I'm suggesting we leave the Idea open for the moment because the CAR might come back as "intended behavior". I played around with control references for a while when I filed this. Notice, for example, when you have a typedef control and you do Create>>Reference on it. Then look at the type of the wire coming out of that reference in context help. The reference is strictly typed, but only to the type of the control -- it does not include the typedef information. It seems like typedefs were deliberately left out of all of the VI Server control relationships, not just the Value property. If that's a deliberate choice, it will require Kudosing an idea to push to have it changed. If it is just a bug, it might get fixed on its own.
Any idea that has received less than 9 kudos within 9 years after posting will be automatically declined.