Browsing through the forum I found an example of the "/Dformat/" token.
This means that the desired feature is already present and I misunderstood the syntax and function of the "/Dformat/" token. Sorry for that!
To get "2022-12-24_Filename.Ext" you need the "custom" token "/Dformat/" where "format" is the placeholder for any desired squence of date-items (yy, yyyy, MM, dd) and it may also contain other characters which are then added exactly as written.
=> The date as written above would need "/Dyyyy-MM-dd/", the complete string would be: "/Dyyyy-MM-dd/_/FN/".
Should you rather prefer a buch of separate date entities you could also use a custom date token for each part of the compound, for example: "/Dyyyy/-/DMM/-/Ddd/_/FN/".
Happy creating your own customized renaming scheme...!
CORRECTION:
CORRECTION:
Browsing through the forum I found an example of the "/Dformat/" token.
This means that the desired feature is already present and I misunderstood the syntax and function of the "/Dformat/" token. Sorry for that!
To get "2022-12-24_Filename.Ext" you need the "custom" token "/Dformat/" where "format" is the placeholder for any desired squence of date-items (yy, yyyy, MM, dd) and it may also contain other characters which are then added exactly as written.
=> The date as written above would need "/Dyyyy-MM-dd/", the complete string would be: "/Dyyyy-MM-dd/_/FN/".
Should you rather prefer a buch of separate date entities you could also use a custom date token for each part of the compound, for example: "/Dyyyy/-/DMM/-/Ddd/_/FN/".
Happy creating your own customized renaming scheme...!