Skip to main content
Solved

Is the "Import..." option on AttributeExposer static?

R
Forum|alt.badge.img

I am using AttributeExposer (AE) and need to import the values from a table. I do not know how many values there are before I run the workspace, so I need to be able to import the values from a table created by the workspace.

I thought I had it all worked out and then realized that the "Import..." option might not be "live." i.e., it worked the one time and has been holding onto the values I entered, rather than repopulating with a newly created table each time.

Is this true? Is this "one and done" and you need to manually reload these values if the table you loaded them from changes?

I need to do this after I use AttributeCreator, because the attributes that are created are invisible. If there was way to create attributes and have them be visible, that would be wonderful.

Thank you,

Randy McGregor

Best answer by erik_jan

Yes, you are right.

The Import function on the AttributeExposer (as on other transformers) is static in a way that it imports the values into the workspace, but does not update automatically when the source changes.

View original
Did this help you find an answer to your question?

6 replies

erik_jan
Contributor
Forum|alt.badge.img+18
  • erik_janContributor
  • Contributor
  • Best Answer
  • December 2, 2019

Yes, you are right.

The Import function on the AttributeExposer (as on other transformers) is static in a way that it imports the values into the workspace, but does not update automatically when the source changes.

R
Forum|alt.badge.img
  • ramcgreg
  • Author
  • December 3, 2019

Thank you. Boy, it would be nice if the fields that I added with AttributeCreator would just show up when I add them.

 

ebygomm
Influencer
Forum|alt.badge.img+39
  • ebygommInfluencer
  • Influencer
  • December 3, 2019

What are you actually trying to achieve? It sounds like you may be trying to create a dynamic workflow, is it necessary to expose the attributes at all?

R
Forum|alt.badge.img
  • ramcgreg
  • Author
  • December 3, 2019
ebygomm wrote:

What are you actually trying to achieve? It sounds like you may be trying to create a dynamic workflow, is it necessary to expose the attributes at all?

I am trying to create a dynamic workflow. If I don't expose the attrbutes, will they be in the final product - A feature class? I do need to see the fields in order to use the AttributeManager, because some values in the field that I am using for field names are not valid (have commas, spaces, etc...) and they need tweaking.

ebygomm
Influencer
Forum|alt.badge.img+39
  • ebygommInfluencer
  • Influencer
  • December 3, 2019
ramcgreg wrote:

I am trying to create a dynamic workflow. If I don't expose the attrbutes, will they be in the final product - A feature class? I do need to see the fields in order to use the AttributeManager, because some values in the field that I am using for field names are not valid (have commas, spaces, etc...) and they need tweaking.

Attributes do not need to be exposed to appear in the writer. Probably worth looking through this article

https://knowledge.safe.com/articles/1050/dynamic-workflow-tutorial-introduction.html

 

nielsgerrits
VIP
Forum|alt.badge.img+54
ebygomm wrote:

Attributes do not need to be exposed to appear in the writer. Probably worth looking through this article

https://knowledge.safe.com/articles/1050/dynamic-workflow-tutorial-introduction.html

 

This. It is hard to see how a lot of users struggle through this part of the learning curve. I know I had a hard time to get my head around it.

Reply


Helpful Members This Week

Community Stats

31,418
Posts
119,136
Replies
39,035
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.