Hi.
While deleting a record with a particular ID I get an in-app error message saying that the record is currently being used in another app.
How to find out which app that is?
Thanks!
Hi.
While deleting a record with a particular ID I get an in-app error message saying that the record is currently being used in another app.
How to find out which app that is?
Thanks!
Hi HCEH,
Good question. That error usually means the record is still used somewhere in your environment. Here are a few ways to find where it’s referenced:
Global Search
In the main Tulip interface, use the top search bar.
Enter the record ID or key value.
This will show any apps, tables, or analytics that include it.
Table Relationships
Open the table with your record.
Go to the Relationships tab.
Look for any related tables pointing to it, then filter those tables for your record ID.
App Dependencies
Search your apps connected to this table.
In each one, check triggers, variables, and widgets that reference the record.
Review analytics or dashboards using the same table.
Search in Other Tables
Open possible related tables.
Use Filter to look for your record ID in key columns.
Active App Runs
Go to Analytics > App Runs to see if any apps currently have that record open.
Check the full error text for clues about which app or table is blocking deletion.
If you still can’t locate it, share the record ID and table name with Tulip Support. They can confirm exactly where it’s being referenced.
Let me know what you find.
Thanks @nicolo.lagravinese
We are currently still on TCC. So Tulip Support cannot help much in this case, nor some of the good suggestions that you have.
A question: aren’t Analysis/Dashboards “read-only”, meaning that the dependency to Analysis/Dashboard should not really be a dependency because the value is not being “used” just shown.
Cheers!
Hi HCEH,
You’re right, analyses and dashboards are read-only, so they wouldn’t block a record from being deleted. That error usually comes from a trigger, variable, or table record placeholder in another app that still points to the same record. Since you’re on TCC, the best option is to open any apps that use that table and check the Table tab in the App Editor. Look through triggers or expressions where the record or table is mentioned and also check step layouts for any table record placeholders. Once those references are cleared, you should be able to delete the record without that message showing again.
Hi @HCEH question: would you be OK force-deleting a record that was in use on some Station (e.g. loaded in an interactive table widget), or is knowing where it is in use crucial for your use case?
We’re considering providing an option that would allow Triggers/Apps to delete table records that are in use, after a confirmation note to the Operator – as is already possible today from the Tables API.
Very interesting question. Initially I was curious to know where the record was used because it was not supposed to be locked in the first place. And if locked, it should be released after some period of time. And after days of time it was still locked, which was telling me that something is wrong with the whole mechanism. The entry should at least be released after the app is cancelled or user has timed-out. And I tried to investigate that, but without transparency where it is used, I couldn’t solve it.
Possibility to delete it even if used can pose some risk and should not be taken lightly. I think it should be a very restricted permission.
I hope that helps clarify it.
Thanks!
@OlgaStroilova It would be 10x more useful to be able to force quit a station from the stations page, rather than this approach