thank you @HBT , the difference to your example is, that I call the action from another table=“Texte” and view “Texte Anzeige Bearbeitung_Detail” not from table “Listen”.
Thanks to your test case, my problem seems to be, that if the CONTEXT() function is used within the SELECT() statement, it has another context and not the context of the table/view from which the action is triggered. If I use the CONTEXT() function without the SELECT() statement it works correctly.
The use case is, to give the user a context sensitive help in table / views where the link to the help documentation url is in the table “Listen”.
Thanks for the explanation, I tested the expression from another table as you said. If the table name in the select statement is the table where the view is located, the statement works.
**But it doesn’t work if you are querying a different table in a Select statement from a view. This is definitely a bug. @Steve **