Invalid date instead of dd/mm/yyyy

sfd_pl
New Member

Hi,

Believe this has been brought up back in 2019 and solution was to regenerate columns. It does not do the trick but instead more date goes missing.

App sheet Invalid Date.pdf (195.5 KB)

Could it because of large data? The table iโ€™m working on is has 20 columns and 6000 rows

Solved Solved
0 3 1,703
1 ACCEPTED SOLUTION

From the image you have shared, it sounds that all invalid dates are where the first two digits are greater than 12. So it sounds that the app or device from where the app is updated is capturing dates in mm/dd/yyyy format and the back end sheet is storing the dates in dd/mm/yyyy format.

In summary there seems to be mismatch in date formats between the app setting or device or browser and the backend data sheet.

You may wish to take a look at the following artilces regarding locales support in AppSheet.

https://www.appsheet.com/Support?q=locale&hPP=10&idx=help&p=0&is_v=1

View solution in original post

3 REPLIES 3

From the image you have shared, it sounds that all invalid dates are where the first two digits are greater than 12. So it sounds that the app or device from where the app is updated is capturing dates in mm/dd/yyyy format and the back end sheet is storing the dates in dd/mm/yyyy format.

In summary there seems to be mismatch in date formats between the app setting or device or browser and the backend data sheet.

You may wish to take a look at the following artilces regarding locales support in AppSheet.

https://www.appsheet.com/Support?q=locale&hPP=10&idx=help&p=0&is_v=1

sfd_pl
New Member

@Suvrutt_Gurjar Thank you for directing me to the solution and works perfectly!

Hello, I have the same problem. What exactly did you do? I have verified that both the Sheet data sheet and the location of the table and Appsheet have the same language (Spanish Colombia) but it still does not work

Top Labels in this Space