Skip to main content
Question

Has anyone else experienced an issue writing a Date field to Excel?

  • July 18, 2017
  • 4 replies
  • 110 views

Forum|alt.badge.img

I have an issue that occurs in ALL of my workflows. Randomly, the first row of data written to Excel defaults to a data type of General and therefore date fields end up in the Excel data format of floating point. Every row thereafter is formatted, correctly, as a date (Custom data type).

Example:

All first row date field(s) format: 41787

All rows after the first row format: Jan 09, 2017

Is there a fix/reason this is happening? This is not a new issue. it's been happening since FME 2016.

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

geosander
Forum|alt.badge.img+7
  • July 19, 2017

Hi @rick_williams,

I can't reproduce this issue with FME 2017 (on Mac...). But I didn't specify a custom data type: I simply set the Type field to "date" and then all rows have the correct formatting (e.g. Jan 09, 2017), also when I don't write the column names.

If you did change the Formatting, what did you fill in in the Custom Number Format field?

Also, what is the attribute value you are trying to write? Is it a string (formatted with the DateFormatter for instance) or a numeric value?


Forum|alt.badge.img

This is a snap shot of my workflow and the results.

My current build is 2017.0.1.1 (20170512 17291 Win64)


Forum|alt.badge.img

This is a snap shot of my workflow and the results.

My current build is 2017.0.1.1 (20170512 17291 Win64)

fme-excel-writer.png

 

 


takashi
Celebrity
  • July 20, 2017

This is a snap shot of my workflow and the results.

My current build is 2017.0.1.1 (20170512 17291 Win64)

Hi @rick_williams, I was not able to reproduce the symptom. If the issue has not been resolved yet, I would recommend you to contact Safe support, sending a workspace that reproduces the issue.