Questions in topic: "workspace compatibility"

What happend with AreaBuilder in 2016.0 and 2016.1

zzupljanin — Mon,10 Sep 2018 13:16:03 GMT

Hi,

So,I've created workspace in 2016.1,ran it,it went perfect.

Then I gave workspace to a colleague who ran it on 2016.0 with same data,some results weren't good at all,specifically creation of donut polygons.The parameters were indeed set to Create Donut = Yes and Drop Holes = No.

There was no Error Message 'These transformers are not in your system...' while oppening in 2016.0.Workbench ran workspace succesfully.

We've already found solution/workaround.While in 2016.0,delete AreaBuilder that was created in 2016.1 and add AreaBuilder.Everything worked as expected.

I was wondering,does anyone know why did this problem occur?

Thanks

Best way to upgrade a Worksapce to the latest version?

tim_wood — Thu,24 Aug 2017 09:47:23 GMT

I've taken some Workspaces created in 2015/2016 and saved them as 2017.0.1.1 Workspaces.I've removed Readers and Writers and added them in fresh.In some cases I get this report in the log:

Workbench: Workspace integrity check during load found one or more readers/writers with configuration issues.

Workbench: Backed up current workspace as: E:\AddressBase\Plus\FME\LACHS (backup).fmw

Workbench: Fixed reader/writer configuration issues.

I know this means the issues should be fixed,but it raised the question in my mind about the best way to upgrade Workspaces.I know old ones should generally run in a later version of FME but in these cases I'm changing the Reader(s) and/or Writer(s) so I might as well update the Workspace version.

Some Workspaces have a lot of transformers in,so is a good upgrade path to create a blank Workspace,add the Reader(s) and Writer(s) then copy and paste the transformers from the old Workspace (then upgrade transformers and edit parameters if necessary)?

Ensuring FME Version and Workspace Compatibility

fmelizard — Wed,24 Aug 2016 18:51:42 GMT

How do I ensure that my workspaces still work in a newer version of FME?

Save As menu to down/upgrade current workspace compatible with a targeted version of FME

bo — Sun,08 May 2016 15:41:45 GMT

This could make FME consultants' life much easier,as their clients may not be able to keep up with the latest versions.This is especially the case with FME servers,the upgrade of which often involves IT departments with their own schedule and procedures to follow.

Add ability to save a workspace as older version.i.e.2015 to save as 2014.

fmelizard — Thu,29 Oct 2015 15:35:00 GMT

Versioning of Readers and Writers

fmelizard — Thu,29 Oct 2015 15:34:52 GMT

Versioning on the Readers and Writers - similar to Version on the Transformers.To know when to delete and add a new reader.Or notify when a reader/writer from an older workspace needs to be deleted because of changes in the format.

ISO 19115-1 compatible Workspace metadata

fmelizard — Thu,29 Oct 2015 15:34:49 GMT

Have the workspace description meet ISO 19115-1 so it can be searched by the metadata in the description and as a service end point

Add a Workspace Explorer to find old workspaces by name or format or transformer content

fmelizard — Thu,29 Oct 2015 15:34:49 GMT

Add a Workspace Explorer to allow me to find all those workspaces I worked on for the past years on my machine up to the level of searching the transformers used within the workspace itself,formats I used ...

Show all Transformers that can be upgraded

fmelizard — Thu,29 Oct 2015 15:34:48 GMT

Allow download of older transformer versions

fmelizard — Thu,29 Oct 2015 15:34:47 GMT

The possibility to download an older version of a transformer/reader/writer.Sometimes the use of an older version of a transformer/reader/writer is more convenient then the latest version.And not everybody has 9 versions of FME installed.

Backward compatibility rollback to older transformer versions using store

fmelizard — Thu,29 Oct 2015 15:34:44 GMT

I would love to have "backward compatability" rollback where i can pull older versions of transformers from store.In case i need to save-as to a lower build target.