If you want to manipulate the attributes you need to explicitly expose them on the featureReader, if you only want to write them, you can use the dynamic setting on the writer. See https://knowledge.safe.com/articles/1157/dynamic-workflow-tutorial-destination-schema-as-a.html

---

If you want to manipulate the attributes you need to explicitly expose them on the featureReader, if you only want to write them, you can use the dynamic setting on the writer. See https://knowledge.safe.com/articles/1157/dynamic-workflow-tutorial-destination-schema-as-a.html

I want to both manipulate the attributes and to write them after manipulation.

 

I always want all the attributes exposed.

 

Basically I want to add as readers all the shapefiles that have a certain text in the name.

 

 

I find it very cumbersome to specify all the attributes that I want exposed.

 

 

Am I totally using the wrong readers to accomplish a task that seems very basic and simple (get a handful of shapes and add them as readers)?

 

 

---

I want to both manipulate the attributes and to write them after manipulation.

 

I always want all the attributes exposed.

 

Basically I want to add as readers all the shapefiles that have a certain text in the name.

 

 

I find it very cumbersome to specify all the attributes that I want exposed.

 

 

Am I totally using the wrong readers to accomplish a task that seems very basic and simple (get a handful of shapes and add them as readers)?

 

 

You can vote on this idea https://knowledge.safe.com/idea/24774/add-import-function-to-featurereaders-attribute-to.html to improve exposing attributes.

 

 

The issue is that the shapefiles to be read in are only determined at run time, so FME has no information as to the schema, until the process has started, so it cannot automatically make the attributes available on the canvas to work with. The attributes are carried on the feature, and are available to the writer (via dynamic schema).

 

 

If you don't want to explicitly expose the attributes to manipulate them, then your other choice is to add a Merged shapefile reader and use wilcards in the merge filter of the feature or in the SourceDataSet parameter or both.

 

That will give you a one-time combined set of attributes of all the files you read in when you added the reader, if the files change, or the attributes in the files change, this will not be reflected on the reader.

 

 

---

You can vote on this idea https://knowledge.safe.com/idea/24774/add-import-function-to-featurereaders-attribute-to.html to improve exposing attributes.

 

 

The issue is that the shapefiles to be read in are only determined at run time, so FME has no information as to the schema, until the process has started, so it cannot automatically make the attributes available on the canvas to work with. The attributes are carried on the feature, and are available to the writer (via dynamic schema).

 

 

If you don't want to explicitly expose the attributes to manipulate them, then your other choice is to add a Merged shapefile reader and use wilcards in the merge filter of the feature or in the SourceDataSet parameter or both.

 

That will give you a one-time combined set of attributes of all the files you read in when you added the reader, if the files change, or the attributes in the files change, this will not be reflected on the reader.

 

 

I appreciate you taking time to help out.

 

I guess I can expose the attributes. My only frustration with this is that I never know how many shapefiled there will be in the folder and I am not so sure all will have the same attributes as to be able and construct the writer and other transformers appropriately.

 

 

I will continue to tweak Python scripted parmas + your suggestions to see with what I can come up.

 

 

---

Hi, has anything changed for this transformer over these years?  I need FeatureReader to read all attributes, preferably without exposing, since they may vary. 

---