To tsdgbe -
I should point out that TestStand 3.0 was supposed to prevent end users from editing NI types but did not because of a bug. TestStand 3.1 fixed this bug and so NI type are not editable. In general we don't want you to edit NI types. The reason why is that future versions of TestStand will make additions to its types and you will loose your changes that you made to them. The documentation for TestStand typically states that if you want to customize an NI type you should copy the type and rename it.
Now when you get the type conflict you are given a choice to select one of two types to use, one that is current and one from the file that is being loaded. You need to use the original NI type and not your edited version and you
must resave any file that contained the altered one.
Did you increment the version of the NI type after you edited it? If you did, this would remove the modified bit on the type and our effort to remove the edited type from you system will require a few extra steps.
Did you save the edited type in the type palettes?
Scott Richardson (NI)
Scott Richardson
https://testeract.com