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?
Best answer by fmelizard
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.
Did this help you find an answer to your question?
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
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.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.