Skip to main content
  • EN
I've had great succes in FME  2012 using attributeValueMapper. In 2013 beta I find it completely bogus - whatever I do the values are mapped from null to null, including the  "default value" field. 

 

 

Opening a workspace created with 2012  and inspecting it I see that my mapping are replaced with null to null relations. 

 

 

This probably means I'll have to revert back to 2012, just as I was starting to appreciating some of the new shiny things of the 2013 beta... :( 

 

 

Or is it some new functionality / logic / whatever that I get wrong? 
Hi Hektopascal

 

Yes the issue you mentioned with opening the AttributeValueMapper in FME 2013 was also identified by our testing team earlier this week. It has been fixed and I believe the fix is included in the current beta on our website now - although this hasn't been restested yet.

 

 

Sorry you ran into this and thanks for mentioning it to the group.

 

 

Cheers

 

Ken  

Reply


Community Stats

30,159
Posts
114,480
Replies
37,806
Members
Terms & ConditionsCookie 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.