Skip to main content
Archived

Add NullAttributeMapper functionality in AttributeManager

Related products:FME Form
erik_jan
Contributor

The "Set Default Value" option in the AttributeManager only works for new attributes.

That forces me to use a NullAttributeMapper for each different default value (multiple attributes).

Adding this to the AttributeManager (Set a default value for Null and Empty attributes) would reduce the number of transformers in my workspace.

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.

2 replies

erik_jan
Contributor
Forum|alt.badge.img+17
  • erik_janContributor
  • Author
  • Contributor
  • December 15, 2016

Just found out that this can be done in the AttributeManager using conditional values at the Set Value option ( If attributes not has a value, set to new value).

erik_jan
Contributor
Forum|alt.badge.img+17
  • erik_janContributor
  • Author
  • Contributor
  • December 15, 2016
But the ability to set the default value for existing attributes without a value would save time setting up the conditional values.

 

 

Helpful Members This Week

Community Stats

31,073
Posts
117,799
Replies
38,834
Members

Latest FME

Terms & ConditionsCookie settings

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.