Deleting entries
Deleting a single entry
Via the row menu. ApptiveGrid asks for confirmation: Are you sure?
Deleting multiple entries
- Select the entries in the table.
- Click Delete {number}.
- Confirm in the dialog Delete {number} entries? with Delete.
Deletion is final
Deleted entries can't be restored within the app. The version history shows changes to field values, but doesn't bring back a deleted entry.
For larger deletion actions, take a CSV export first.
When deletion doesn't work
Delete not possible. The entry is still referenced elsewhere.
Or, naming the referencing entry:
Delete not possible. The entry is still referenced by {entry}.
The entry is connected to another entry via a link. Remove these references first.
If the message names the entry, go straight there
In the second variant, it states which entry holds the reference — that saves you the search.
If it doesn't, switch to the referencing Grid and filter on the link column. For Link record, a filter on the relevant value takes you directly to all affected rows.
This safeguard is intentional — it prevents references pointing into thin air.
Be careful with filtered views
You're deleting real entries, not rows of a view
A view only shows a subset. But deletion always acts on the Grid — afterward, the entry is gone from every view.
Before a bulk deletion, make sure the filter matches exactly what you mean. A look at the count in the delete dialog helps: if it's unexpectedly high, the selection is off.
Deletion and flows
There's no trigger for deleted entries
The available triggers react to new and changed entries, not to deletions. So a flow can't react to a deletion.
If something should happen on "removal," use a status field instead: set the entry to Canceled instead of deleting it, and have the flow react to that change.
Alternatives to deleting
Hiding is often better
| Instead of deleting … | Approach |
|---|---|
| Old entries clutter the overview | Filter the view, e.g. to the last 12 months |
| Entry is finished | Status field set to Done, view filtered on it |
| Entry was a mistake | Deleting is the right call here |
| Data must be retained | Don't delete — filter |
Filtered entries still count against the plan-dependent number of entries per Grid. If that matters, deleting is the only option — but with an export beforehand.
Deleting the Grid instead of entries
If the entire dataset should go, deleting the Grid is the more direct route. Check beforehand whether views, forms, flows, or pages access it.