Great question—this is such a common frustration when working with LabVIEW Typedef clusters, especially when you’re trying to clean up tab order without breaking existing code. Let’s break down why this happens and how to fix it:

Why the References Get Messed Up #

LabVIEW’s Typedef cluster references rely on the index position of the control inside the cluster, not its label or name. When you reorder controls in the Typedef, LabVIEW automatically updates existing references to point to the same index position (not the same labeled control) to avoid immediately breaking every VI that uses the Typedef. That’s why your references are now pointing to the wrong labeled controls—LabVIEW prioritizes index consistency over label matching.

Solutions to Keep References Tied to Labels #

1. Use Control Names (Not Cluster Indexes) for References (Best Long-Term Fix) #

Ditch index-based references entirely and use control names to target specific controls in the cluster:

• First, make sure every control in your Typedef has a unique, fixed "Name" property (right-click the control → Properties → Appearance → Name—this is different from the visible label).
• Instead of using "Unbundle By Name" or index-based reference retrieval, use the Get Control Reference function. Feed it the cluster’s reference, then specify the target control’s name in the "Control Name" input.
• This way, no matter where you move the control in the cluster, the reference will always find the right one as long as the name stays the same.

2. Adjust Tab Order Without Reordering Controls (Quickest Fix for Your Original Goal) #

If you only need to fix tab order (not rearrange the visual layout), you don’t have to move controls at all:

• Right-click the cluster → Advanced → Reorder Controls.
• In the pop-up dialog, drag the controls to set your desired tab order. This changes the tab sequence but leaves the cluster’s internal index positions (and thus your existing references) completely untouched.
• This is the easiest way to get the tab order you want without breaking any references—total win.

3. Backup and Manually Fix References (If You Already Reordered) #

If you’ve already reordered the Typedef and need to fix existing references:

• First, take screenshots or export the XML of all VIs that use the Typedef’s references (to remember which label should map to which reference).
• Open each dependent VI, and manually update references:
  • For "Unbundle By Name" nodes, re-select the correct labeled control from the dropdown.
  • For Get Control Reference calls, update the "Control Name" input to match the correct control’s name.

4. Advanced: Custom Property Binding #

For super robust, future-proof references (great for large projects):

• Add a custom property (e.g., "ReferenceID") to each control in the Typedef (right-click control → Properties → Custom). Assign a unique ID to each control.
• When retrieving references, loop through all controls in the cluster, check their custom "ReferenceID" property, and grab the reference that matches your target ID. This works even if you rename controls or reorder them later.

Final Recommendation #

If your main goal is just fixing tab order, go with Solution 2—it’s fast and zero-risk for your existing code. For long-term project maintainability, switch to Solution 1 to avoid this problem entirely in the future.

内容的提问来源于stack exchange，提问作者Sparkler