Report time stamps and graphs wrong format and other reporting issues

Hi,

Greeting for the day.

Thanks for the feedback. I will send the PM for more details.

Regards,

Rana Sharma

Hi,

Greeting for the day.

Thanks for the feedback. I will send the PM for more details.

Regards,

Rana Sharma

Hi Rana,

just to clarify what I posted. I said the dates are in the wrong format, I did not say they were wrong.

Most of the my reporting issues appear to have been fixed in this version, which is good to see.

Ian

Hi,

Can you please post the format you see?  Also please post the desired/expected format as well to help the team contrast the two.   Thank you!

Hi Rob,

The format I see is yyyy-mm-dd, the format I expect to see is dd-mm-yyyy.

The example below is from my Mac Book Pro.

Ian

Hi Ian,

YYYY-MM-DD is ISO 8601 standard and is a universal standard that leaves no ambiguity as to the numerical ordering. I would disagree that changing the date format to localised datestamps would have  any benefit.

Why would you prefer DD/MM/YYYY or MM/DD/YYYY (satans datestamp) over ISO 8601?

Emile

Very simply because the Australian standard is dd/mm/yyyy and forget that other datestamp, that just isn't logical.

Apple and MS disagree with you, but that is the nature of the world.

Ian

Hi Emile,

further the Sophos forum allows you to choose the date format to use in your posts, so why not the Sophos XG?

Ian

Hello

I will agree with Ian, report dates should always be in the as per the region. This helps while working with reports in excel format else excel will not be able to handle date in the correct format.

Regards, Ronak.

Hi,

Greetings for the day!

Good to hear from you ,most of the reporting issue has been fixed.

Coming to Date format

Currently Data are showing in YYYY-MM-dd format which is ISO 8601 standard and it is fixed format. User cannot configure it.

But Yes , We would like to take your feedback on that , what is your expectation with date format ?

Regards,

Rana Sharma

Hello Rana Sharma

The best date format would have as per appliance region.  This helps when reports are exported in CSV format and open with excel. As excel picks the date format from regional setting and if the data is not in the same format it will format date as text. Also, it is easy for an admin to correlate dates the format in which they are use to.

Regards, Ronak.

While I am also a DD/MM/YYYY person living in the UK, I don't think I have ever seen Excel have an issue with ISO 8601. In fact, with Excel 2016 that i've just looked at, it has auto localised it for me which is a setting I can change. I do appreciate there is a difference on the PDFs being ISO 8601 but do you have any examples where Excel fails to automatically re-format as date?

This is what I have consistently seen when using Excel:

Just trying to understand if i'm not seeing a problem that others get.

rfcat_vk 

"Apple and MS disagree with you, but that is the nature of the world."

Actually, they don't because they also are ISO 8601 compatible but for general use they have elected for localisation over the ISO standard because for a general user it may not be easier to read but it is what they are used to. I am referring to the use of ISO 8601 in a network security device where log and report detail makes more sense in that format so it starts from largest digit to smallest digit. Using it in DD/MM/YYYY HH:MM:SS although also correct is harder to read on a 1000 log line output.

Emile