Anticipating on future: we now have a series of surveys than should run in the longer run. Everytime a new instance of the survey is launched, I manage it through a dedicated token, so all the data entered is stored/tagged properly.
That's great! However, as we go, I have more and more tokens in my token table and - although not yet a problem - I envisage this profusion of tokens may in the longer run be a source of confusion.
At first, I had though that the results in the results table were merged with the tokens - so that each entry would be token-tagged "forever" - and that I could simply delete the unwanted tokens. However, it seem it is not the case and the values of tokens visible in the results table are just a view of joined tables and deleting them would results in thos entries no longer being tagged.
My question therefore: is there a way of more simply hiding the unwanted tokens? Some sort of a filter I guess, or any other way you are using for the same purpose?
The administrator has disabled public write access.
Hiding (?) old/unwanted tokens
3 years 1 month ago #97047