Bug: Error in FileGlobal when upgrading 3.5 -> 22

[Yamaeda]

So, we're upgrading a "fairly" old test system for a customer and is working on upgrading TestStand and LabVIEW versions. We upgraded TS3.5 -> TS2022Q4 (LV7.1 -> LV2019, WinXP -> W11) and everything looked fine. When trying to start, it complained about a missing instrument and we assumed the MAX configuration was erroneous. Luckily the old computer still works so we could start it and compare and after a while we noticed something ... interesting.

The instrument was referred to in a FileGlobal and that import/upgrade had bugged, it had set the Comment as Value! Two of the parameters had comments and both got the same error, all others was correct.

Has anyone heard of this before?

[Yamaeda]

Ok, it seems we've gotten files from 3 different test systems. It's probably different instrument naming conventions between them ...