Skip to content
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

Filename of Model.BIM backups uses incorrect timestamp #967

Closed
edhans opened this issue Jul 31, 2023 · 2 comments
Closed

Filename of Model.BIM backups uses incorrect timestamp #967

edhans opened this issue Jul 31, 2023 · 2 comments
Assignees
Labels
issue: bug Confirmed as a bug in TE3
Milestone

Comments

@edhans
Copy link

edhans commented Jul 31, 2023

Describe the issue
I think there is an issue with the naming convention used for Model.BIM backups when a ZIP files is saved after each model save.

The filename created is:
Backup_ModelName_YYYYMMDDhhmmssnnn
YYYY - Year
MM - Month
DD - Day
hh - Hour
mm - Minute
ss - Second
nnn - milliseconds?

The problem is hour. It doesn't seem to handle AM/PM. I saved a model at 2:24pm (14:24 military time) and the file name is Backup_Model_20230724022423678. The bold should be 14 I believe, otherwise there is no way to tell if that is AM or PM.

** Which version are you currently using? **
Tabular Editor 3.9 Enterprise

Windows 10.

@DBojsen
Copy link
Collaborator

DBojsen commented Aug 3, 2023

Hi @edhans

Completely agree - added to backlog as a bug.

Best Regards

David - Tabular Editor 3 Support

@DBojsen DBojsen self-assigned this Aug 3, 2023
@DBojsen DBojsen added the issue: bug Confirmed as a bug in TE3 label Aug 3, 2023
@DBojsen DBojsen added this to the 3.9.1 milestone Aug 4, 2023
@DBojsen DBojsen modified the milestones: 3.9.1, 3.10.0 Aug 16, 2023
@otykier
Copy link
Collaborator

otykier commented Aug 23, 2023

Fixed in 3.10.0. Thanks for reporting!

@otykier otykier closed this as completed Aug 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue: bug Confirmed as a bug in TE3
Development

No branches or pull requests

3 participants