Hello Daniel,
I suggest a customfield type 'sql' with 3 depending param options for the following ones, marked with $, plus the StrOption as textfield.
SELECT $PARAM_id FROM $PARAM-table WHERE $PARAM_other_customField = 'StrTextinput';
where $PARAM_id is saved to database, could be extended with 'as'
and $PARAM_other_customField wants to be query in behind (LEFT JOIN) which queries the results of #__matukio_customfields (or similar, I did not check the exact name by now). That would result in more complex statements for the frontend views, too.
So for now, I would like to focus the quoted statement which should meet most needs and would be a base query I maybe would like to extend later || on the fly.
I need such 'clean query' inside Matukio because I do develop a site these days with Seblod CCK plus Matukio while both frontend views and types (lists, detailviews) should be 'linked' to each other.
I am thinking about developing such a sql-customfield by myself - would you be interested in it for core-implementation? But firstly, please also review the last entry to
compojoom.com/forum/107-wishlist/20924-c...ultiple-select#35625
(i was asking about the status which Yves set up) - because if you will change the models to work with the J!3.7 customfield types and remove the compojoom ones, that would change a lot, of course.
By the way, your Kunenas Code modal popup has errors
Kind regards,
Pierre.