Solution
This behavior can occur when the LabVIEW Unit Test Framework parses network-published shared variable nodes that use complex cluster or nested cluster type definitions.
To work around this issue, create Unit Test Framework tests for isolated logic VIs instead of directly testing the top-level VI containing the network-published shared variables.
- Open the top-level VI in the LabVIEW project.
- Isolate the application logic into a dedicated subVI.
- Configure the logic subVI inputs and outputs using standard cluster controls and indicators based on the same cluster type definition.
- Pass data from the network-published shared variable nodes in the top-level VI to the logic subVI terminals.
- Create the Unit Test Framework test (.lvtest) for the logic subVI rather than the top-level VI.
- Verify that all controls, indicators, array elements, and cluster elements throughout the VI hierarchy use unique label names.
- Recreate the test and verify that the duplicate control label error no longer occurs.
This architecture separates network-published shared variable access from application logic and reduces exposure to Unit Test Framework parsing limitations associated with shared variable nodes that use cluster-based type definitions.