Override Invalid Entry

[tvinci]

Is there a way to override the error message in red letters so the user can submit the form regardless?
Thanks!

[WillowMobileSys]

You don’t want to override this error. It is making sure that data of correct type is getting placed into the column. Bad things can happen otherwise. This is why we have data types.

There are several ways to prevent the error depending on your intent.

I suspect you have the columns defined as “LatLong”? If so then that is not accurate based on the names. LatLong’s are pairs of values. When splitting them you want to define the individual parts as Decimal. So redefine each column as Decimal and you would be good based on the above example shown.

[tvinci]

Dear John,

Thanks for your response! The data types are already decimals.

[tvinci · Accepted solution]

Solved: I converted the data types to LongText.

[WillowMobileSys]

I’m glad you worked out a solution.

Just a caution. I specifically avoided suggesting a Text data type based on the column names.

If you define them as Text you are basically allowing ANY value, even those that are invalid for Latitude and Longitude usage.

Decimal IS the correct data type. If they were defined that way and you were still getting an invalid error message, that means the values, even though they LOOK like decimal, were not actually decimal. To understand why, we would need to look at where you are getting the values from and how the are being assigned to the Latitude/Longitude columns.

I don’t know how you are using the columns, so Text/LongText might just work out to be okay.

[tvinci]

I do not believe Float values are supported in AppSheet but that’s what the values are, floats, because they have many decimal places behind them. But I think LongText will work out because only certain admin users can edit the values. Thanks!

[Steve]

tvinci:

I do not believe Float values are supported in AppSheet

Decimal values are floats.

[WillowMobileSys]

Steve:

Decimal values are floats.

Agreed! I think of Decimal as being a subset of Floats.

Decimals have a limited range of values but can represent those values precisely. It is still a large range suitable for all applications except the most extreme scientific computations.

Floats have a much larger range of values but can lose precision because of the way they store the represented value.

---

More importantly for this thread. Latitude and Longitude values have a standard representation of up to 3 digits to the left of decimal and 8 digits to the right of decimal - both negative and positive.

These values are well within the range of a Decimal type. If given the choice to store as Decimal or Float, Decimal is the best choice.