Skip to main content
Solved

CSV Reader parameters

  • November 1, 2024
  • 1 reply
  • 54 views
smithgk
Contributor
Forum|alt.badge.img+6

Hi, I’m having some problems working with the CSV Reader. I created a Reader from a CSV that has 3 fields: Address, City, and ZIP. I have ‘Case Sensitive Field Names’ and ‘Enforce Strict Schema’ set to No, but then if I modify my source CSV to have the attributes: address, city zip, and Notes, the Reader fails to read in any data.

What am I doing wrong here? It seems like even though I changes some properties for the Reader, it is defaulting back to the original schema that I input when creating the Reader. Any help is greatly appreciated.

 

Best answer by bwn

Unless you are doing dynamic reading/writing, you will still need to modify which Attribute Names to expose to the workspace.

An initial Reader setup will automatically do an initial scan of the source data, and default to exposing all fields/columns found as Attribute Names to the workspace.   If during Reader setup this was Address, City, ZIP……..then that it will be these columns the Reader will by default be set to Expose to the Workspace (if present in the Source).

If you change the field names in the source, the Reader will still read the Feature data in, but any fields/columns that are not called Address, City, ZIP will be read as unexposed Attributes.

This is fine in dynamic read/write situations where the workspace does not care generally what fields are Exposed in the workspace of not.   However if you have downstream Transformers that depend on these being exposed for their own Parameter settings, then you will need to either go and change the Reader Attributes to Expose setting or use a separate AttributeExposer.

View original
danilo_fme
1 person upvoted this
  • danilo_fme
    danilo_fme
Did this help you find an answer to your question?

1 reply

bwn
Evangelist
Forum|alt.badge.img+26
  • bwnEvangelist
  • Evangelist
  • Best Answer
  • November 4, 2024

Unless you are doing dynamic reading/writing, you will still need to modify which Attribute Names to expose to the workspace.

An initial Reader setup will automatically do an initial scan of the source data, and default to exposing all fields/columns found as Attribute Names to the workspace.   If during Reader setup this was Address, City, ZIP……..then that it will be these columns the Reader will by default be set to Expose to the Workspace (if present in the Source).

If you change the field names in the source, the Reader will still read the Feature data in, but any fields/columns that are not called Address, City, ZIP will be read as unexposed Attributes.

This is fine in dynamic read/write situations where the workspace does not care generally what fields are Exposed in the workspace of not.   However if you have downstream Transformers that depend on these being exposed for their own Parameter settings, then you will need to either go and change the Reader Attributes to Expose setting or use a separate AttributeExposer.

danilo_fme
1 person upvoted this
  • danilo_fme
    danilo_fme

Reply


Helpful Members This Week

Community Stats

31,224
Posts
118,410
Replies
38,827
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.