Select to view content in your preferred language

Pro 3.3.5 Odd date format when creating export folder

82
4
Friday
Labels (1)
ThomasHoman
Frequent Contributor

Hello,

When I am creating a new folder in Pro as part of the  sharing/exporting a pdf to, the date format is really wonky - please see attached. Windows Explorer shows the correct date. so I don't think it is the OS.

I am curious if others have observed this behavior and if their are suggestions for correction. Due to some vendor constraints we are currently unable to move beyond this version.

Thanks for ideas to correct.

Regards,

Tom

0 Kudos
4 Replies
JamesPoeschel
Frequent Contributor

Weird, I dont remember having that issue when I had pro 3.3.5. I have 3.5.0 now and still dont have that, but I dont see any mention of this bug after skimming the 3.4 release issues addressed document. 

You could try this:

Verify your Windows region settings (Control Panel → Region → Formats → “Additional settings” → Date) to confirm they’re set to MM/dd/yyyy.

Check ArcGIS Pro’s application language (Options → General → Language).  Make it “English (United States)” assuming you are in the US. 

 

 

Here's what my region settings looks like in the control pannel. JamesPoeschel_0-1760119325098.png

Not sure anything else you could do but update PRO. 

0 Kudos
DanPatterson
MVP Esteemed Contributor

List of date formats by country - Wikipedia

ISO 8601 - Wikipedia

It is the international date format used by most countries, so it isn't wonky, just different than you expect.  Check your settings as suggested above


... sort of retired...
0 Kudos
RTPL_AU
Honored Contributor

@ThomasHoman  
Definitely a known issue in 3.5   BUG-000176711
Can't remember seeing it on 3.3.5 though.

From what I can tell this is only a visual issue and if you check the folder in a file manager it should be correct.

@DanPatterson  I can hand-on-heart say Australia has not moved to 32 month years... yet....  🙂

 

0 Kudos
RTPL_AU
Honored Contributor

@ThomasHoman @JamesPoeschel 

After a quick check - it is known in 3.3  as BUG-000169961

0 Kudos