Skip to main content
Solved

Feature Reader not exposing attributes from table

  • September 24, 2025
  • 10 replies
  • 94 views

jugoslaviaa
Enthusiast
Forum|alt.badge.img+6

Hi everyone,

I’m running into an issue when using the FeatureReader transformer.

When I read a table through the FeatureReader, the attributes are not exposed  However, if I read the same table directly using a normal FME reader (through SDE or GDB), all the attributes are properly exposed.

Is there a setting I’m missing with the FeatureReader that prevents the attributes from being available? Or is this expected behavior when using it compared to a standard reader?

Thanks in advance for any advice!

Best answer by nielsgerrits

I think the steps are:

  • Set Regenerate to Parameter change. OK to apply.
  • Configure FeatureReader with a file, set one outputport per feature type, select feature types to read. OK to apply.
  • Set regenerate to Never. OK to apply.
  • Set dataset dynamic, the outputports will now stay as initially configured.
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, 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.

10 replies

virtualcitymatt
Celebrity
Forum|alt.badge.img+47

User attributes are usually exposed, at least if an output feature type is exposed. Do you have a screen shot you can share with us?

If you are reading though the generic port then they usually aren’t exposed. 


nielsgerrits
VIP
Forum|alt.badge.img+61

By default, output ports are generated one per feature type?

Attributes are unexposed when the generic port is used.


jugoslaviaa
Enthusiast
Forum|alt.badge.img+6
  • Author
  • Enthusiast
  • September 24, 2025


@virtualcitymatt This is how it looks 

 


nielsgerrits
VIP
Forum|alt.badge.img+61

The features are leaving from the Generic port, this is why they are unexposed.


jugoslaviaa
Enthusiast
Forum|alt.badge.img+6
  • Author
  • Enthusiast
  • September 24, 2025

But i chose one per feature type in my setting 


nielsgerrits
VIP
Forum|alt.badge.img+61

Is the input dataset an attribute or a parameter? Because if the input is dynamic the outputports are dynamic. But nowadays you can configure the outputports using a file, then set Regenerate to Never and change the dataset to something different.


jugoslaviaa
Enthusiast
Forum|alt.badge.img+6
  • Author
  • Enthusiast
  • September 25, 2025

Yes, both Connection and Features Types to Read are attribute from inititor
 

 


jugoslaviaa
Enthusiast
Forum|alt.badge.img+6
  • Author
  • Enthusiast
  • September 25, 2025

@nielsgerrits I wanted to test your suggestion. I am selecting the dataset but it still sends to the generic port ‘

 

 


jugoslaviaa
Enthusiast
Forum|alt.badge.img+6
  • Author
  • Enthusiast
  • September 25, 2025

Ok. I found the problem it is was not my setting but COM Component which did not allow me to expose the attribut


nielsgerrits
VIP
Forum|alt.badge.img+61
  • Best Answer
  • September 25, 2025

I think the steps are:

  • Set Regenerate to Parameter change. OK to apply.
  • Configure FeatureReader with a file, set one outputport per feature type, select feature types to read. OK to apply.
  • Set regenerate to Never. OK to apply.
  • Set dataset dynamic, the outputports will now stay as initially configured.