Hi, after having discovered a bug in uri->get('type') in Seblod backend (https://github.com/Octopoos/SEBLOD/issues/356), I think I found another problem in Dynamic Cascade: uri->get('id') seems not to work in select dynamic cascade ehn used in the final stage/behavior (it seems to work in the Start stage).
it should work both with and without quotes for integers. Anyway here it does not work here both in back-end and front-end.
I am getting somehow troubled in using select / select dynamic in a flexible way:
there is no way of using field values in the SQL - there is a long thread here proposing a hack https://www.seblod.com/community/forums/fields-plug-ins/select-dynamic-with-fields-variables
trying to tune the SQL retrieving the Seblod content type has a bug in backend and (I recently discovered) also a bug in frontend when editing (it works in adding an item) - https://www.seblod.com/community/forums/fields-plug-ins/uri-getvalue-bug-in-saving-select-dynamic
now getInt seems not to work in dynamic cascade in End stage.
Are point 2 and 3 being looked at? Any chance of having a feature addition for point 1?
removing options can be done with plain jQuery, why are you suggesting of using select2 (or chosen or a similar select enhancement plugin)?
Now, I have read in the forum that only removing options is supported and not adding: no chance of adding? I ask this because if it's like that, the SQL query must be very general (like all items in #__content) to be filtered later on, being a very long (and thus slow) list...
can take a look in existing dynamic cascade how it does ajax requests,
perhaps simplest solution would be to fix existing one to pass current
url variables to the ajax request, this is all that is missing.