Any issues using different versions of FrameMaker?

[Samala]

Up to this point, I've been the only one in my group to use FrameMaker and I'm using the 2022 version. I've created all the content and set up the book files. My coworkers want to start editing these files  but they're using 2020. Today, one of them tried to open a book file and received an error. They want me to save all the files as 2020 files. I'm urging them to upgrade to 2022 instead, but in the meantime they want me to save the files as 2020 so they can make small edits. I thought I would check here to see if there could be any issues with doing this because I will still have to open the files, generate the TOC, and fix any issues with the book or files, etc. Then I'll have to remember to keep saving them as 2020 files.  It seems like the best approach would be for everyone to upgrade to 2022.

[Jeff_Coatsworth · Accepted solution]

Yes, you are correct - updating all of them to the same version makes the most sense.

[Samala]

Thanks!

[frameexpert]

There shouldn't be any issues saving down to 2020 from 2022. You can only directly save down to the previous version. If you need to save down further (for example, from 2022 to 2019) then save as MIF (Maker Interchange Format).

[Samala]

Thank you. After I posted here, I tried saving one file in the book as 2020 and received the "Saving as previous version will result in loss of information related to new features" message. I realize that I'm probably still okay but I don't want to take any chances.  I appreciate your response though!

[Dave Creamer of IDEAS]

Your options are:

1. Save as 2020 and you switch to that version unless there is a critical feature you need in 2022. You can keep 2022 installed but be careful double-clicking on a file to open it--it might open the wrong version. Depending on your license and assuming you have access to the installer, you might be able to install and run 2020 without extra cost.

2. As Jeff mentioned, everyone can upgrade to 2022.

[Samala]

Thank you. You pretty much summed up my concerns...what happnes when I open the file again or what if I forget to save the file as 2020? We work for a large corporation that has an enterprise license. We can't install anything on our computers - we have to go through IT. The more I think about it, the more I think the safest route would be for all of us to have the same version on our machines.

[Dave Creamer of IDEAS]

The ability to save down a version or as MIF is _not_ a good workflow on a back-and-forth basis. It should only be used in special circumstances. 

[Bob_Niland]

Samala: what happnes when I open the file again or what if I forget to save the file as 2020?

Then it will have to be opened by someone with a newer version of FM (perhaps even a trial verison on a naive machine), or they can try the "heroic open" hack.

While I agree with David that MIF is not an optimal interchange scheme for team document workflow, MIF is wise routine project practice. This is particularly true for situations where the document has to be sent out for translation. You never know what FM version the shop will have.