"Down Rev" a VI?

[MarkBowles]

I'm working on a system in LabVIEW 2020 with an HMI on Windows, and a NI cRIO 9067 as the "brains of the outfit."

There's a small test program in the package that operates on a cRIO 9148, which is not supported by LabVIEW after 2019.  So, I have a separate copy of LabVIEW 2019 on my development system, and whenever I (infrequently) have to modify this program, I just switch to it.

I'd like to copy a couple of rather intricate, carefully-developed VIs from the big app (LabVIEW 2020) to the test program (2019).  But, when I attempt this, LV 2019 rejects these VIs because they were last touched by a future version of the software.  There's nothing in them that's particularly advanced, but apparently the version numbers themselves being incompatible is too much for LV 2019.

Is there a way to force LV 2019 to consider the content of the VIs and ignore the version numbers, and "down-rev" them to 2019? I tried putting them in a separate folder and mass compiling them, but the mass compiler rejected them also.

Thanks,

-- Mark

[Kyle97330]

There is a "Save for previous version" option in the menus.  You have to do it from the newer version.

The other thing that will only sometimes work is that if you alter the VI once on an older version, then check the box in VI properties to "Separate compiled code from source file" on the VI properties screen, if you then open it in a newer version it will usually (but not always) not want to resave the VI if you don't make any changes.