New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
option to not coerce dates to strings #16
Comments
of course my workaround breaks the round trip of reading the xlsx back in to R. So now my workaround is to do a vlookup in excel that converts the date to a string by wrapping the lookup value in the TEXT() function. so now my vlookup into the file generated by writexl looks like:
It would still be cleaner if writexl wrote a date in a format that excel recognized as a date. |
Just for further reference, there is a date bug as well in Excel. They had some issues with that in readxl. |
Would anyone share me the reason that writexl chooses to coerce the Lines 36 to 38 in e8d176c
|
Should be fixed now! |
Thanks! |
It would be really useful to be able to keep dates as dates that can be read by excel. xlsx files are not really a great way to store data, but they are a great way to feed data into excel. keeping dates as excel readable dates would make a lot of sense in a bunch of use cases.
btw for now I am using this as a workaround:
dplyr::mutate(df, date = as.numeric(date - as.Date(0, origin="1899-12-30", tz='UTC')))
where df is my dataframe and
date
is my column that contains dates.The text was updated successfully, but these errors were encountered: