So I've been developing spotfire smartsheet connected dashboards for a while and use date types as format. Noticed spotfire is reading the dates strange adding extra 00s while in smartsheet date format is logical and was correct in dd/mm/yy format
This was due to a change in API response. Should be resolved now
Related
My application exports data into Excel friendly HTML.
With a specific mso-number-format value it is possible to show date or time in a local format. However i know only six such values:
Short Date
Medium Date
Long Date
Short Time
Medium Time
Long Time
.NET offers powerful mechanics of defining localized date format with format specifiers.
Is it possible to map .NET format specifiers in mso-number-format values?
I am reading data from an excel sheet and the 5th column is a date field. I have the following logic to ensure that the input date is converted to YYYY-MM-DD format -
var valid_from = new Date(data[counter][5]);
valid_from_new = var formatedDate = moment(valid_from).format("YYYY-MM-DD");
reqBody.valid_from = valid_from_new.toString();
I have the date 2017-10-10 to begin with and I am able to read it fine via my node app. It works for me as long as I do not edit this field in my Microsoft Excel 2010. If I edit it or simply find/replace the values, I get unix default date (1970-01-01) in reqBody.valid_from.
To find out what happens after the replacement, I checked that if I replace 2017-10-10 with 2017-10-20 and then "clear formats" (excel utility), I get 43028 displaying in the sheet, whereas for the date 2017-10-10 it remains the same, i.e. 2017-10-10. I don't understand why excel behaves like this.
Can this be handled uniformly by my application? I just want to make the "YYYY-MM-DD" format work across any excel versions. It would be fine if I could do one format change or clear format once before feeding the file and it would work.
I don't understand why excel behaves like this.
Excel behaves like that as it stores 2017-10-10 as a serial date. Meaning it is an integer representing the number of days that have past since January 1st 1900 for the Windows system. (potentially 1905 or something similar for mac). In your specific case its apparently 43028. It displays a converted date in a format people read as 2017-10-10 in your case. You will note this as your formatting for the cell is either a date of some sort or a custom user format. If you entered the date as text by leading it with a ' you would note the format does not change when you change the cell formatting. The date is actually just text and not a formatted date. Numbers that are enter in a format that looks like a date to excel, excel will usually attempt to automatically convert them to a serial date value for you. It has a built in list of formats it looks for and I believe also looks at your system settings format too.
As a side note, the decimal portion of the number represents time. Fraction of a day. 0 is 00:00:00 and .5 is 12:00:00.
Can this be handled uniformly by my application?
I am sure the answer to this is "yes" but is beyond my expertise. I highly suspect it is because your code is handling it as text initially. Things go wrong when it receives the integer from excel that represents the date in excel.
When I try to export in excel a list of incidents from HPSM I have an issue; the date has different formats: "dd/mm/yyyy hh:mm" or "mm/dd/yyyy hh:mm:ss". It is a problem because when the day and the month are both less the 12th then I don't know which is month or which is day.
Is it a possibility to have the same format or to create a program to do this?
I don't know HP Service Manager, but please consider exporting the data into two different files, one for each date setting, as CSV or Excel.
Then you can use tools like Power Query or the Text Import Wizard to open the files and set the origin date format of the column. Excel will then show that date column in your PC's regional settings format.
Have a large raw data dump and I am trying to format the dates into a consistent format.
As you can see from the screenshot, there are two main formats, one custom mm-dd-yyyy hh:mm AM/PM and mm/dd/yyyy hh:mm:ss. One is stored as general, while the other as a custom value.
I've tried to =left(A2,8), converting via text() and using text to columns, but can't bring the values to a consistent value.
It appears that your Windows regional settings for Short Date are DMY or similar. It is likely your data dump is in MDY format. That is why A2 and A4 are being converted to "real dates" (although incorrectly), and A3 is not since Excel does not know what do with month = 13. You will note that A2 is 1-Dec-2015 and I suspect that in the original data it is 12-Jan-2015.
EDIT: To expand a bit on the explanation. When something that looks like a date or time is entered into an Excel cell, Excel tries to change the result to a date, parsing the input according to the Windows Regional Short Date format. This sometimes has an undesireable outcome. For example, if your Windows Format is MDY but the date is input as DMY, input with days <=12 will be converted incorrectly, and input with days > 12 will be retained as text. This behavior cannot be "turned off" and causes many complaints from those who want to enter data that looks like a date, but is not. (For example, entering an odds ratio as 1-10 or 12:3 will get converted to a date or a time)
Several options
Change the output of the data so as to have the dates in DMY format.
Instead of OPENing the data file, do a Text Import. In later versions of Excel, you will find this on the Data Ribbon ► Get External Data ► From Text. This will open the Text import wizard and allow you to specify the MDY format of the incoming data before Excel transforms it.
After you have done one of the above, the result will be a "real" Excel date or date/time and you can format it how you like.
Write a IF() where if column B specifies "Custom" change format to standard.
For AM, just remove it(replace AM with nothing). For PM add 12 to the hours and replace PM with nothing.
For custom Replace - with / and append :00 to add the seconds to the custom ones too.
I want a customized format(with milliseconds also) in such a way to handle for a date and time in Microsoft Excel.
Sample date and time:
08.25.2010 00:52:09.359
For understanding of above sample date time, it is 25th August 2010 12 hrs 52mins 9seconds 359 milliseconds(AM).
Please provide a custom Format to handle the above mentioned sample date and time and finally to apply for a column.
In Excel 2003 I use the following for time with fractions of second:
"hh:mm:ss,000"
(note: my decimal point is a "," - German)
so a time entered as 12:13:14,1516 will be displayed as 12:13:14,152
Hope this works for you
Edit 28-Nov-2012
I recently migrated to Excel 2010. Special format using up to 3 zero's after a comma for seconds as described above still works. More than 3 zero's however are not accepted.
I'm not certain what you mean by "not recognizing the dates" but the following custom format would give you the format you're looking for. You'll have to adjust the millisecond separator "." according to your localization, of course.
mm.dd.yyyy hh:mm:ss.000
Applying it to a column is as easy as right clicking the column header, selecting Format Cells, choosing Custom on the left and pasting that format string into the Type box.
If you're trying to enter dates in this format, I don't believe that Excel will support that. I don't know of any option to set the date separators to a "." for Excel. Even setting the date format to use dots under the Regional and Language Options doesn't make Excel recognize that.