Common Error Messages
The messages are listed here verbatim, so you can search for them.
Data and entries
Cannot delete. This entry is still referenced elsewhere.
Cannot delete. This entry is still referenced by {reference}.
Both messages have the same cause: the entry is connected to another entry via a link. The second variant additionally names which entry references it — so you can go straight there.
Solution: First remove the links pointing to this entry. If the message doesn't name the referencing entry, a filtered view in the referencing Grid helps you find all affected entries.
This is a safeguard — it prevents dangling references. → Linking Grids
Cannot change. This field is used in a filter.
You're trying to change the type or name of a field that a filter points to.
Solution: Remove the filter in the relevant view, change the field, then set the filter again. The filter can be in any view of the Grid, not just the one currently open.
Links to Grids that are already linked elsewhere are not yet possible.
You're trying to link to a Grid that is itself already linked somewhere else. Chains of links are not possible.
Solution: Flatten your data model, link directly to the target Grid, or retrieve the value via Use linked value. → Linking Grids
The name already exists
Field and Grid names must be unique.
The name can be a maximum of {max} characters long.
Shorten the name.
No matching entry found.
There's no match in the selection dialog for a link.
Common cause: The target view of the link is filtered, and the entry you're looking for is excluded by the filter. Check the target view's filter.
Row filtered
Not an error, but a notice: you've changed an entry so that it no longer matches the view's filter, and it's now hidden.
The entry is not deleted. In an unfiltered view, it's still there.
This Grid has been updated
Someone else has changed the Grid. Reload the view to see the current state.
Input
Please fill in this required field.
A field marked as required is empty.
Only numbers (0-9) are allowed
The field is of type Number and only accepts whole numbers. For decimal places, use Decimal or Currency instead.
Only floating point numbers are allowed
The value doesn't match the Decimal type. Check the decimal separator.
A valid e-mail address is required
The input is not a valid e-mail address.
Please enter a valid phone number
An international dialing code is required (e.g. +49)
Phone numbers need a country code.
Tip for form creators: Point this out in the field description, or incorrect entries will pile up.
Please enter a valid URL
Enter the full address, including https://.
Must be in the format Latitude, Longitude (e.g. 50.12,6.543)
Geocoordinates as two numbers separated by a comma; the decimal separator is a period.
Please fill in the required subfields
An address field is incomplete.
Unrecognized date format:
The entered or imported date can't be read. This commonly happens during CSV import.
The option must not be empty · The option must not be a duplicate
Applies to the option list of Single Select and Multiple Select.
Filters
All existing filters must be valid
A filter condition is incomplete. Complete it or remove it — until then, the filter has no effect.
Filter conditions can only be nested 3 levels deep
You've reached the maximum nesting depth.
Solution: Create a helper field of type Formula or Checkmark that captures the complex condition, and filter on that. → Filtering, Sorting, Grouping
Expressions and formulas
The expression editor's messages are in English and name internal type names such as ASString.
ASString class has no function named …
This function doesn't exist for this value type. Most common cause: the expression yields a different type than expected at this point — after .isEmpty(), for example, it's a boolean, not text anymore.
Solution: Check the displayed type (Type: … above the sample result) and use the functions for that type. → Function reference
function needs 1 arguments
The parentheses contain too few or too many values. The number required per function is listed in the function reference.
Unexpected token …
The expression is incomplete or written incorrectly — a missing parenthesis, a trailing period, double quotes instead of single ones, or a comma used as a decimal separator. → Syntax
No field with id …
The expression refers to a column that no longer exists. Re-insert the field using the picker.
No message, but no result either
The most common case doesn't produce an error message at all: an unknown name — a mistyped key, a misspelled function name — is treated as an empty value.
| Observation | Likely cause |
|---|---|
| Formula column stays empty | Expression reaches into nothing, or an involved field is empty |
| Block never appears | Wrong key in the visibility rule |
| Block always appears | Faulty expression — a block stays visible on error |
| Filter returns nothing | Condition doesn't evaluate to a boolean |
| Placeholder in Flow text stays empty | The path to the value is wrong |
Sign-in and registration
These messages appear on the login page, before the application has even loaded.
Login failed
We were unable to log you in. Please check your email address and password.
The email or password is wrong.
Solution: Check what you entered; otherwise reset your password. If the account was created through Google, Apple, or Microsoft, there is no password — only the matching button will get you in.
Session expired
Your sign-in has expired or could not be completed.
The login page was opened directly — from a bookmark, for instance — or sat open for more than half an hour.
Solution: Choose Sign in again. The bookmark belongs on app.apptivegrid.de, not on the login page. → Session expired
Approval required
This message comes from Microsoft, not from ApptiveGrid: your organization doesn't allow external applications to sign people in without administrator consent.
Solution: Send the request to your administrator from the dialog, if it offers that. ApptiveGrid is cleared once in Microsoft Entra. → Signing in with Microsoft
We were unable to create an account with the email and password you entered.
Registration failed. The message doesn't name the reason — so also check whether an account already exists for that address.
Solution: Check the details; if the account already exists, sign in or reset the password instead. → Creating an account
We could not reset the password.
The reset link didn't work, or the password wasn't accepted.
Solution: Trigger the reset again and use the link from the most recent email. → Forgot password
Required · Min 3 characters · Use at least 8 characters · Please enter a valid email
Validation on the sign-up form. First and last name need at least 3 characters; the password needs at least 8 and at most 128 — beyond that the form reports Use at most 128 characters. The same password check applies when resetting it.
Access and sharing
You no longer have access to this Space.
Your permission has been revoked. Contact the owner of the Space.
This Space has been deleted
Not allowed
Your role doesn't permit this action.
Access to this form is restricted.
The form link has an access restriction that you don't meet — for example Any registered user or Anyone in this Space.
Solution: Sign in, or ask the form creator for access. → Access to shared content
This view is no longer accessible.
The shared view has been deleted, or sharing has been removed.
This Space is already shared with this user
The person already has access. Change their role instead, in the Shared with list.
Spaces cannot be shared with themselves
You entered your own address.
No user exists with the e-mail
There's no ApptiveGrid account for this address. Check the spelling; otherwise the person needs to register first.
Exceeding the licensed seats on your plan
You've invited more people with editing rights than you have seats for.
Solution: Downgrade roles to View — that's free — or purchase additional seats. → Seats
Flows
Flow still has errors
A step is incompletely configured. Go through the steps; the affected one is marked in the editor.
No previous run was found.
You want to start a Flow using the data from the last run, but there hasn't been one yet.
Solution: Test it normally first. → Testing Flows
There's no custom UI set up for this step. If you need a UI, you can add it in the Flow Editor.
A Flow step is meant to show a page, but none is assigned.
Common cause: The assigned page was deleted. Check which page is set on the Show page step.
This process step could not be loaded
With the addition:
The current step could not be executed due to a faulty configuration or an invalid value.
Please contact the person responsible for this process or your organization's administrator.
End users see this message. As the person responsible, check the run history — under Show error details it shows which step failed.
JavaScript could not be generated
AI generation in the JavaScript step failed. Refine the description and try again.
Pages and portals
This view has no summable numeric columns
The Sum Card needs a column of type Number, Decimal, or Currency in the embedded view.
Common cause: The column exists but is hidden in this view.
This view has more than {maxRows} rows. The sum only covers the first {maxRows} rows.
Not an error, but important: the displayed sum is incomplete.
Solution: For reliable totals, use a grouping with an aggregate or a field of type Calculate sum.
Input fields without a name or id are not included in the Flow payload.
Applies to the HTML with form fields block. Without a name or id attribute, the value is lost.
{count} file(s) could not be uploaded
The most common cause is the plan-dependent size limit.
Preview error
The HTML block contains faulty code.
Forms — what people filling them out see
Oops - Error
General error message on submission.
Warning: Potentially risky form
The form has been flagged as potentially abusive. Open anyway lets you continue.
As the form creator: Contact abuse@apptivegrid.com to request a review.
This form has been locked
The form has been locked. Also contact abuse@apptivegrid.com.
Never reveal your password.
Not an error, but a security notice on every form. Never enter passwords or credentials in forms.
No message, but still a problem
Some things happen without any error message:
| Observation | Cause |
|---|---|
| A button is missing | Missing permission → I don't see a button |
| A Flow doesn't start | The trigger points to a different Grid or form |
| A Flow starts endlessly | An action writes to the Grid that triggers it |
| An entry has disappeared | It's excluded by the view's filter |
| A field is missing from the form | The column type has no form field, e.g. Rich Text |
| A portal shows too much data | The embedded view isn't sufficiently filtered |
| A formula column stays empty | Typo in the expression → Expressions and formulas |