I am having an issue getting attributes from a custom transformer output exposed in the main workspace.
The output in question was added after the custom transformer was created, but appears to me to be all in order.
The Population_Base output exposes it's attributes correctly while the Meshblock_Base output doesn't. Here is an image of the Meshblock_Base properties.
And finally what it looks like on the Main workspace.
I can't figure out why these 2 attributes are not being exposed.
Am I missing something obvious, or is there something fishy going on?
I am using FME 2018.0 32 bit.
Best answer by elhastino1
So it looks like this issue was more about Feature Readers and Parameters, than exposing attributes. It appears that no recognisable features are getting to the output which is why they are not being exposed successfully in the Main workspace.
I have used a Feature Reader inside the custom transformer that is using parameters for the input File Geodatabase and Feature Class. When using these parameters the Feature Reader reads nothing. I have tried a couple of things and reverting the Output Ports to a single Generic output, and then using an AttributeExposer works successfully.
Initially this Output Port was set to One per Feature Type, and the port seemed to be named successfully for the file I was using, but not being used. Clearly using the Generic port is better in hindsight, as the user could use a feature class with a different name.
So it looks like this issue was more about Feature Readers and Parameters, than exposing attributes. It appears that no recognisable features are getting to the output which is why they are not being exposed successfully in the Main workspace.
I have used a Feature Reader inside the custom transformer that is using parameters for the input File Geodatabase and Feature Class. When using these parameters the Feature Reader reads nothing. I have tried a couple of things and reverting the Output Ports to a single Generic output, and then using an AttributeExposer works successfully.
Initially this Output Port was set to One per Feature Type, and the port seemed to be named successfully for the file I was using, but not being used. Clearly using the Generic port is better in hindsight, as the user could use a feature class with a different name.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
