"Release Date" and "Update Date" column of the IPS Signature Export formatting incorrectly

[MKnox]

Hello, this is my first post, so apologies if posted in an incorrect category.  

Is there a way to configure the date format in SmartConsole prior to exporting to csv?

When I export the IPS signatures from the R80.10 dashboard, the csv output appears to be generated with two formats in the Release/Update Date columns (columns C & D).  I don't recall having this issue in R77.  The dashboard view within SmartConsole shows the date format to be DD/MM/YYYY, yet only a subset of the exported signatures follow this format.  The other signatures appear to be formatting as MM/DD/YYYY.  Along with the mismatch date formats, the values are inputted differently as well, either as MM/DD/YYYY or DD-MM-YY.  This makes filtering the output challenging as I show some release dates coming up as December 2, 2019 when it should be February 12, 2019.  Formatting the columns after the export doesn't appear to effect the way excel interprets the values (there may be a setting in Excel to address, If so, please let me know.  My excel limitations are just not familiar one).  

Thank you in advance, 

Marcus 

[Omer_Shliva]

Hello Marcus,

Can you please share some examples and screenshots?

[MKnox]

Here's a snippet of that output.  

[Omer_Shliva]

Hi,

Please send me the Excel.

Omersh@checkpoint.com

[G_W_Albrecht]

First question would be why you need to do this anyway... But i would just leave these two columns in text format instead of date !

[MKnox]

Thank you for your response.  Previously I would use the output for metrics primarily.  I don't recall having the date format issue in R77.  I attempted to change the format of the two date columns to "text" and got the below output. 

Before format to text:             

24-11-09
15-01-07
25-12-16
1/10/2009
1/10/2009
19-05-13
5/5/2013
5/5/2013
5/5/2013

After format to text:

24-11-09
15-01-07
25-12-16
39823
39823
19-05-13
41399
41399
41399

[MKnox]

Appears to be a known issue, sk117537.  Will wait for it to be addressed in a future release.  I have workarounds until then.  Thank you for your time.