#54 Missing API access (state: open)

Since I can get the filter options as id, I have the problem that I need the meta information from the parent table/metamodels. The current API has to less/zero points to get the information. I need more information: ID => To data from the parent Table Alias => To data from the parent Tabel or simple make the "getSelectMetaModel" public. Or better add more functions like,

getFilterRow($id); // Return the whole information for the filter by the id,
getFilterRowByAlias($alias) // return the whole information for the filter by the alias.

This should be a basic function for all attribute. We need more access to the information.

What do you need it for? What is the use case? Your comment is way too abstract for me to understand, please elaborate.

Sometime the filter must be more than just a name. (Thanks to the designer.) For example i create another MetaModel with the fiter options. The fields are: Name, Alias, Picture, Description, etc. Now i am using the MetaModels-Filter CE/Mod, because i don't want to rebuild the search functions by my own. But i have to make a custom template. Because the screen design tells me, i have to output the name, the picture, the dircroption etc. But i only get the key and the name.

So i ending up with another request on the same table to get the missing Meta-Inofmration to build the HTML with the image and so on.

So my idea is, that the filter options for selects and tags should return more than this, like they do it on the RAW part of the items with the SELECT_RAW or TAGS_RAW part.