Timesheets Preferences Module

[Beto Boton]

Hello

 

As you will notice, I'm working like mad on starting point to get it customized to taste!

 

I found this issue with DATE FORMATTING. I use "the rest of the planet" date format DD/MM/YYYY which is my system date format.

Everything goes OK until now. I tried to change a payment period from monthly period to weekly and the date assigned to start and end period reverted to MM/DD/YYYY.

Question: How do I get dates to respect the system date format( DD/MM/YYYY)

Here is a screenshot

[Jonathan Hogle]

Enter Layout made and select the field you wish to change.

in the Inspector, go to the "Data" tab.

In the "Data Formatting" section, make sure the date option is selected, and choose "Custom"

You can now enter the date however you would like it displayed.

 

P.S.

You also have the option of a short and long system date, which I believe would work in your case.

 

Thanks

-JH

[Fitch]

Have you tried File > File Options > Text tab, "Always use current system settings" ?

There is also Ye Olde Trick of saving a clone of the file. That will reset the date format the first time you open the clone.

[Beto Boton]

Thank you guys, BUT that is not it. 

1- "Always use current system settings"  That is set and works fine for other dates in other fields

2- In the "Data Formatting" section, make sure the date option is selected, and choose "Custom" - This option is greyed out on the inspector (field is not locked)

The selection of weekly bi-weekly etc is calling script 1218 Set_Pay_Period_Suggestions, and the date after this script is reversed to MM/DD/YYYY beside the field contains DD/MM/YYYY. 

I was not able to completely understand how it is reverting to an American style date.

APPARENTLY this is where it is happening but NO CLUE why
SetField [T14_PREFERENCES::Pay_Period_Start_Day_Adj ;  Get ( CurrentDate )- Mod (   Get ( CurrentDate ) -  T14_PREFERENCES::Pay_Period_Start_Day_Adj   ;7 )]

Thank you

Beto Boton

 

[OlgerDiekstra]

 

2- In the "Data Formatting" section, make sure the date option is selected, and choose "Custom" - This option is greyed out on the inspector (field is not locked)

 

That would suggest the field is not a date field. Perhaps check in the Table what field type it is.

[Beto Boton]

It is a TEXT field, it gets formatted via the script I mentioned.

[comment]

This is a known issue: when you set a text field to the current date (or a derivative of current date), the result will ignore the file's setting and always use the date format stored with the file.

Either change the field type to Date, or clone the file as explained earlier by Fitch (or both).

[Jonathan Hogle]

Yes, What we did in our UK version of FMSP is changed the field type to a date field and custom formatted it to be DD/MM//YY

[comment]

Yes, What we did in our UK version of FMSP is changed the field type to a date field and custom formatted it to be DD/MM//YY

Formatting has very little to do with this.

[Beto Boton]

THANK YOU

Just changing the field to a date type apparently did the magic.

 

CHEERS
Beto Boton

Australia