Many thanks for the help. Sorry for the long response. Everything works, your table is cool and convenient. As I wrote above, I made a stupid mistake due to my carelessness (instead of “views” there was a “view”), I had previously removed the underscore.
Now back to my original difficult question. Today I added an explanation to topic about the classifier. I think now I managed to describe what exactly I want to do. If you want, I can send the Russian version wherever it is convenient for you.
In short, and keeping the focus only on your table, the task comes down to creating a variable in the FROM field (dv.pages), the value of which is set using a button, which in the worst case calls tp.system.prompt, in the field of which manually enter the hashtag code #UDC/x/x/x, and in the best case, call tp.system.suggester, which shows a hierarchical list of topics in text form (excluding user interaction with the digital hashtag code). It’s true that such functionality is not easy to achieve (the reason for the monstrosity of the diagram), but I think it’s worth it.
In addition, given the logic of your table with the Where field, where the Suggester list is formed based on a summary of all attribute values from all entities that match the value in the FROM field, adding the ability to influence the FROM value will result in filtering of attribute values in the Where fields, which in my opinion will significantly improve the efficiency of your table when you have a large number of entities and a large number of attribute values.
In any case, thanks for the existing table.