Skip to main content
Question

2013 workspace fails on 2011 - what to do ?

  • November 21, 2013
  • 7 replies
  • 10 views
G
Forum|alt.badge.img
Hi all,

 

 

I've recently built a workbench file/workspace to facilitate a conversion of data. It works on the files I've been given.

 

 

I'm using the 2013 version, and have included some Chopper transformers in the work flow. The client - it now appears - is still running a 2011 version, and running it on WinXP too.

 

 

The client's FME Workbench issues an error about "Chopper" being for a newer version when opening the workbench file, and fails to produce any output data.

 

 

What are our and the client's options to remedy this unfortunate situation ? The client cannot upgrade unfortunately, as his department is currently under  decommisioning.
Did this help you find an answer to your question?

7 replies

david_r
Celebrity
  • david_rCelebrity
  • November 21, 2013
Hi,

 

 

the official stance from Safe is that workspaces are guaranteed to be backwards compatible only, i.e. that FME2013 is able to run workspaces written on older versions.

 

 

The other way around nothing is guaranteed and there is a good chance that it won't work, as you've discovered.

 

 

The easiest solution might be to install both FME2013 and FME2011 on your machine (separate directories) and copy/paste as much as you can between the two.

 

 

David
davideagle
Contributor
Forum|alt.badge.img+21
  • davideagleContributor
  • Contributor
  • November 21, 2013
Your problem is because Transformers have revised versions sometimes in new FME versions. This issue is easilly fixable assuming it's just the Chopper that is effected in this instance.

 

 

1) Send the FMW to the client.

 

2) Ask them to open it and dismiss the warnings.

 

The workspace will open with all transformers apart from the Chopper.

 

3) Ask them to search for the Chopper in their Transformer gallery, add it to the canvas unconnected.

 

4) Save the FMW and send it back to you.

 

5) You can now add the Chopper into the correct position and test it to see if it still works in the new way you've been accustomed to, though be aware you may have fewer parameters as you now have the older version.

 

 

Alternativly you could just ask the customer to add a Chopper from 2011 to a blank workspace, save it and send it to you. You can then copy and paste the old version from their workspace into yours and compare the two. More info here:

 

 

http://fmepedia.safe.com/articles/How_To/Transformer-Versions

 

http://docs.safe.com/fme/html/FME_Workbench/Default.htm#Transformer_Version_Numbers.htm

 

http://fmepedia.safe.com/articles/How_To/Transformer-Versioning

 

http://fmepedia.safe.com/articles/How_To/FME-Versions-and-Workspace-Compatibility

 

 

Cheers, Dave
G
Forum|alt.badge.img
  • gispro
  • Author
  • November 26, 2013
Thanks Dave and David,

 

 

We got the client up and running, but I'll keep your suggestions in mind for when I encounter a similar problem.

 

 

Is there a comprehensive list of transformer-vs-program versions somewhere ? It would be beneficial to know which transformers are problematic when downgrading a workspace (and copy/request them in advance from the old version).

 

 

Cheers.

 

davideagle
Contributor
Forum|alt.badge.img+21
  • davideagleContributor
  • Contributor
  • January 7, 2016
davideagle wrote:
Your problem is because Transformers have revised versions sometimes in new FME versions. This issue is easilly fixable assuming it's just the Chopper that is effected in this instance.

 

 

1) Send the FMW to the client.

 

2) Ask them to open it and dismiss the warnings.

 

The workspace will open with all transformers apart from the Chopper.

 

3) Ask them to search for the Chopper in their Transformer gallery, add it to the canvas unconnected.

 

4) Save the FMW and send it back to you.

 

5) You can now add the Chopper into the correct position and test it to see if it still works in the new way you've been accustomed to, though be aware you may have fewer parameters as you now have the older version.

 

 

Alternativly you could just ask the customer to add a Chopper from 2011 to a blank workspace, save it and send it to you. You can then copy and paste the old version from their workspace into yours and compare the two. More info here:

 

 

http://fmepedia.safe.com/articles/How_To/Transformer-Versions

 

http://docs.safe.com/fme/html/FME_Workbench/Default.htm#Transformer_Version_Numbers.htm

 

http://fmepedia.safe.com/articles/How_To/Transformer-Versioning

 

http://fmepedia.safe.com/articles/How_To/FME-Versions-and-Workspace-Compatibility

 

 

Cheers, Dave

This whole topic has now got some significant news. Transformer 'versions' now have much more visibility thanks to new functionality added in FME 2016. See the comprehensive blog posting from @Mark2AtSafe recently here.

https://blog.safe.com/2015/11/fmeevangelist140/

david_r
Celebrity
  • david_rCelebrity
  • January 7, 2016
davideagle wrote:

This whole topic has now got some significant news. Transformer 'versions' now have much more visibility thanks to new functionality added in FME 2016. See the comprehensive blog posting from @Mark2AtSafe recently here.

https://blog.safe.com/2015/11/fmeevangelist140/

Hi Dave

Will this have an impact on the issue brought up by the OP? I'm not sure I see how, or am I missing something?

Would this change make it possible to "downgrade" a transformer to a specific version, so as to enable a workspace to run on an earlier version of FME?

David

erik_jan
Contributor
Forum|alt.badge.img+18
  • erik_janContributor
  • Contributor
  • January 7, 2016
davideagle wrote:

This whole topic has now got some significant news. Transformer 'versions' now have much more visibility thanks to new functionality added in FME 2016. See the comprehensive blog posting from @Mark2AtSafe recently here.

https://blog.safe.com/2015/11/fmeevangelist140/

This only helps in determining what transformers need to be replaced by older versions.

So, it will be good for debugging workspace failures.

It does not repair or prevent compatibility issues.

davideagle
Contributor
Forum|alt.badge.img+21
  • davideagleContributor
  • Contributor
  • January 7, 2016
davideagle wrote:

This whole topic has now got some significant news. Transformer 'versions' now have much more visibility thanks to new functionality added in FME 2016. See the comprehensive blog posting from @Mark2AtSafe recently here.

https://blog.safe.com/2015/11/fmeevangelist140/

Both of you are correct of course - I was simply highlighting that transformer versions are now so much more visible to the end user such that hopefully it'll now raise awareness of incompatibilities and make them less common rather than a thing of the past.

I don't think this kind of incompatibility is practical for Safe to address with a software solution, other than coming up with a way to resolve workspace version control. So, education on the subject and greater visibility of versioning and version control is a helpful way to try to nip these issues in the bud.

Apologies if I muddied the waters... I'm just a little too excited about the new functionality as I've been begging for it for too many years!

Reply


Helpful Members This Week

Community Stats

31,468
Posts
119,287
Replies
39,085
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.