Hi @jneujens, I was able to reproduce the same symptom, but I don't know if it's a defect of FME. Hope someone from Safe clarifies this > @NatalieAtSafe
A possible workaround is to configure dynamic schema based on schema feature(s) read from the resource Excel file by a Schema (Any Format) reader. Note that the schema features have to arrive in the writer feature type before data features.
Alternatively, a different method described in this article can also be applied, if you can replace the resource with a newly created lookup table.
Dynamic Workflows: Destination Schema is Derived from a Lookup Table
Hope this helps.
Hi @jneujens, I was able to reproduce the same symptom, but I don't know if it's a defect of FME. Hope someone from Safe clarifies this > @NatalieAtSafe
A possible workaround is to configure dynamic schema based on schema feature(s) read from the resource Excel file by a Schema (Any Format) reader. Note that the schema features have to arrive in the writer feature type before data features.
Alternatively, a different method described in this article can also be applied, if you can replace the resource with a newly created lookup table.
Dynamic Workflows: Destination Schema is Derived from a Lookup Table
Hope this helps.
Thanks for your help! Good to know you are facing similar issues.
If I find time, I might look into using lookup tables.
Hi @jneujens, I was able to reproduce the same symptom, but I don't know if it's a defect of FME. Hope someone from Safe clarifies this > @NatalieAtSafe
A possible workaround is to configure dynamic schema based on schema feature(s) read from the resource Excel file by a Schema (Any Format) reader. Note that the schema features have to arrive in the writer feature type before data features.
Alternatively, a different method described in this article can also be applied, if you can replace the resource with a newly created lookup table.
Dynamic Workflows: Destination Schema is Derived from a Lookup Table
Hope this helps.
I found that you can use the Schema (Any Format) reader as a workspace resource, instead of the Excel reader. Maybe this is the correct answer.
I found that you can use the Schema (Any Format) reader as a workspace resource, instead of the Excel reader. Maybe this is the correct answer.
That's interesting... I will try this out!
takashi Your solution solved the problem indeed! Thanks!
Hi @jneujens, I was able to reproduce the same symptom, but I don't know if it's a defect of FME. Hope someone from Safe clarifies this > @NatalieAtSafe
A possible workaround is to configure dynamic schema based on schema feature(s) read from the resource Excel file by a Schema (Any Format) reader. Note that the schema features have to arrive in the writer feature type before data features.
Alternatively, a different method described in this article can also be applied, if you can replace the resource with a newly created lookup table.
Dynamic Workflows: Destination Schema is Derived from a Lookup Table
Hope this helps.
Hi
@jneujens and
@takashi. It seems like when using a Reader as Resource, changes to attributes should be picked up on every read but if a new tab (I assume this means new sheet) is added that won't be picked up during schema discovery. Resource reader will only use the feature types (tabs/sheets) set in the `Feature Types to Read` parameter.
Also, Excel and CSV may be a special case where there is no schema when reading the source (or using it as a reader as resource option in dynamic writing). CSV only has one feature type name `CSV` or the file name (without the extension) depending on the option selected when reader is added.
This
other question uses the Schema (any format) reader to get the schema of CSV files and pass that across to the destination CSV file. This approach may be suitable for you.
Hi
@jneujens and
@takashi. It seems like when using a Reader as Resource, changes to attributes should be picked up on every read but if a new tab (I assume this means new sheet) is added that won't be picked up during schema discovery. Resource reader will only use the feature types (tabs/sheets) set in the `Feature Types to Read` parameter.
Also, Excel and CSV may be a special case where there is no schema when reading the source (or using it as a reader as resource option in dynamic writing). CSV only has one feature type name `CSV` or the file name (without the extension) depending on the option selected when reader is added.
This
other question uses the Schema (any format) reader to get the schema of CSV files and pass that across to the destination CSV file. This approach may be suitable for you.
NatalieAtSafe ?? that is indeed what I was seeing. I could even add the new excel sheets as feature types in my 'reader as resource' but nothing was coming out.
I found a way by using the generic schema reader, but thanks for your answer! ;)
Hi @jneujens and @Takashi Iijima,
So glad to find your posts & discussions here.
I'm facing the similar issue, the problem is that my input Excel is not directly output into another data format, but acts as the Supplier of a FeatureMerger transformer, merged with the other input data (IFC) and output to another data format (CityGML). It failed to dynamically read different Excel files (different for file name, sheet name, attribute name&values) if i just change the Excel Reader to Generic Reader (or Schema Reader) for this case. Do you have any ideas/suggestions for my issue? Thanks in advance!
I've done dynamic related settings, not sure if I did correctly:
- EXCEL Reader setting
- Writer setting
As I'm newbee to deal with EXCEL in FME, any detailed illustrations would be much appreciated.
