Best way to upgrade a Worksapce to the latest version?

What I would personally do is re-add the readers and writers, to make sure they're up to the latest version, and then go through the Updateable Transformers list and, if necessary, update them.

Then you'd still have the issue that a new transformer can replace a bunch of old ones, unfortunately there's no way to do that automatically so you'd have to keep an eye on those developments.

@tim_wood

In my experience it is best to open and save the workspace in each version if you can afford to do that. Meaning, opening in 2015 , saving it then 2016 saving it then 2017 and saving it. This would sound silly but copying from 2016 and pasting in 2017 might work as well.

As @redgeographics solution should work as well.

What I would personally do is re-add the readers and writers, to make sure they're up to the latest version, and then go through the Updateable Transformers list and, if necessary, update them.

Then you'd still have the issue that a new transformer can replace a bunch of old ones, unfortunately there's no way to do that automatically so you'd have to keep an eye on those developments.

just right click on reader or writer and upgrade to latest version, no need for re adding them.

 

 

But you need to take care, with writers that are dynamic, sometimes it revert to default settings, and if you a published parameter that is no longer valid, it will be removed, as i found out in SQL Server non-spatial writer

 

 

Just a thought, but is it possible to do benchmarking of transformers/readers/writers for each release and make a table that notes if performance increased to be able to see performance enhancements (if any), and if so, how much? For example the big thing with 2019 was that the Dissolver/Shapefile reader: https://www.safe.com/blog/2019/04/fme-2019/ but what about the others? With how things are moving to being based in FME Hub, Maybe an automated service could do the testing for each version?

We do actually benchmark all our transformers to see if performance increases (or decreases), using automated tools, and we're improving those processes continuously. But we don't generally release the figures, and I'm very loathe to suggest that we do because it can vary so much by data specifics, and it's often easy to misinterpret.

For example, in 2019.1 the PointOnAreaOverlayer is potentially 100-200 times faster than before... but I wouldn't promote that number because it applies only for areas with large boundaries (>256 vertices) and/or donuts with many holes. So there are some HUGE benefits, especially in extreme geometries, but not everyone will see them. That makes it really difficult to publish any meaningful figures like "average" performance.

So... I suggest you keep asking this sort of question, to keep us on our toes, but I don't see us exposing all of our performance numbers in the near future. Not to say it won't happen eventually, and you will see more numbers from us as our measurement tools improve, but right now I don't see a big public dashboard of performance numbers coming.

Actually the biggest thing to be aware of now is the bulk mode/feature tables. The biggest gains occur when we convert a transformer to support these, but the entire workspace is only faster when all of its transformers are converted. So the StatisticsCalculator got this in 2019, but it only becomes faster if it receives data in bulk mode, and passes it to a transformer that supports it. So keep an eye on announcements for transformers supporting bulk mode, because the more that do the more likely your entire workspace will run quicker.

Hope this is of interest. In short, our automated testing is improving, and as it does we'll be in a position to release more information. But right now there's no plan I know of to create the tool that you're suggesting.

I would go trough the list and upgrade them yes.

But relating transformers, like mergeerrs, spatial) relators etc., have had the option to merge attributes under a roll down menu. You'll fnd that you have to actually activate those.

Also if you have nested customrtansformers and pass data through parameters ...we'll you might have your work cut out. As the treatment of those have seriously changed.

I had some where rather then the parameter content it suddenly show the parameter names. Some I had to actively fetch, using parameterfetcher.

 

Also I found that depending on the version of the transformere, creating an attribute in a Attribute creator and using it in the same attribute creator does not necessarily work.

 

So yeah, backup and go trough conversion and test a lot.