Skip to main content
Question

What happend with AreaBuilder in 2016.0 and 2016.1

  • September 10, 2018
  • 2 replies
  • 4 views

zzupljanin
Contributor
Forum|alt.badge.img+4

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

2 replies

david_r
Celebrity
  • September 10, 2018

I'm suspecting that FME wasn't perfectly identifying version conflicts back then, but someone from Safe will have to confirm.


xiaomengatsafe
Safer
Forum|alt.badge.img+3
david_r wrote:

I'm suspecting that FME wasn't perfectly identifying version conflicts back then, but someone from Safe will have to confirm.

Hi @zzupljanin, I second david_r's answer. While workspaces created in a newer version of FME can not be guaranteed to work in a older version of FME, we should provide warning to indicate potential issues like this. If you encounter similar problem in our most recent versions (2018, 2018.1) please do let us know.

 

Glad to hear that adding AreaBuilder in 2016.0 produces the right result.

 


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