Skip to main content
Question

FeatureWriter using xlsx giving out fme_* attributes as rows

  • September 13, 2018
  • 4 replies
  • 20 views

Forum|alt.badge.img

How and why are these created when they aren't visible?

Like:

Type Count

 

fme_feature_type 0

 

fme_geometry 0

 

fme_type 0

 

QA_Camera pos. 0

 

QA_Clock position of obs. 0

 

QA_Comments 0

 

QA_CP value 0

 

QA_Date of Observation 100

 

QA_Depth extra points 0! Resend

regards

andre

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.

4 replies

xiaomengatsafe
Safer
Forum|alt.badge.img+11
Hi @andre, can you attach your input data and the workspace that exhibit this problem? It might be difficult to know what's happening without seeing those. Thank you!

Forum|alt.badge.img
  • Author
  • September 14, 2018

Hi, @xiaomeng. I can send you a fmwt file but isn't too keen on posting it here. I'm on FME Esri Edition build 18305.


Forum|alt.badge.img
  • Author
  • September 14, 2018

Hi @xiaomeng, just found that this issue is a bit of a non-issue thing. The reason for my written xlsx file had such fme_* events was due to attributeexploder->aggregator in the _attr_name. So by simply remove such values all is good. Thanks, andre


xiaomengatsafe
Safer
Forum|alt.badge.img+11

Hi @xiaomeng, just found that this issue is a bit of a non-issue thing. The reason for my written xlsx file had such fme_* events was due to attributeexploder->aggregator in the _attr_name. So by simply remove such values all is good. Thanks, andre

Hi @andre, happy to hear that you've figured out the cause of the problem and fixed it! Great work!