Customize error messages

Roadmap Feature Requests
1

We should be able to customize the error messages like “User email already exists” or “Invalid email or password” and so on…

2

Error messages are correct, but they are in English, which is a problem if you create a non-english app.

3

@christophe-asselin-de-beauville-1: So it’s more of a improve multi-language support issue than a customize the error messages?

4

Tony Dehnke: For now, we can customize error message per field, but when someone makes a mistake during the login process on our app for example, if the password is wrong, a popup is displayed with this error title: Invalid email or password
So it would be great to be able to customize this kind of error messages as well.

Image 1
Image 1329×420 10.3 KB

Image 2
Image 21080×2154 108 KB

5

Tony Dehnke: This may be a different problem (multi-language vs. custom messages) but they may have a common solution. Creators often want to have a lot of control over the language/tone across their product since it’s part of their brand. Custom strings across the app seems like a good value-add for makers who need that level of customization. Multi-language support seems like a bigger effort than custom strings, so it could be that you get more mileage from offering custom strings and letting non-English makers use that to swap the language (even though that wouldn’t be the intent of the feature).

6

We should be able to add error messages for add or update actions. For example: When a user changes the email address there will be no update, if the email(= primary key) already exists. But there is no option to provide an error message to the user. The only workaround I found is to use a modal popup for confirmation of the changes. This will obly show up when the update was successful.

7

Error handling in general is pretty awful, updating a date field in one record with a date field (but blank / null) from another table seems to make the whole action fail, would be nice for Adalo to tell inexperienced coders:

  1. The record update action failed to execute
  2. Why!
    We are all used to stepping through code, if we could do this, it would let us know which specific action was causing the issue. At the moment there is a lot of trail and error.