Bug? user entering invalid time with the format "12:470" causes sync to get stuck

I have a table with a Time column. It works fine, but if a user inputs “12:470” instead of “12:47”, the input is accepted, but on sync the following error is seen:

Unable to update row in table ‘Operations’. → Value ‘12:470’ in field ‘time’ cannot be converted to type ‘Time’.

There is no Valid If rule triggered?
Can you try adding a Valid If rule to check if, for example:

[_This]>"00:00:00"
1 Like

Thanks, but that didn’t resolve the problem.

Also, I don’t feel like I should be needing to mess around with valid-if rules for a standard data type. The system already checks against all sorts of other misformatted time entries, but this particular one is not caught, and then leads to catastrophic failure of the client that must be manually recovered. In my case I had to write ~50 lines of fairly annoying python to get the data out of the manual recovery format and back into my app.

Well, I was trying to provide a workaround not an explanation of why things doesn’t work as you expect.

There is support for that:

https://www.appsheet.com/Support/Contact

Guide on How To Create a Community Post - Google Cloud Community

1 Like