Replies: 4 comments 1 reply
-
It is needed for M2M and M2M as well. Can someone help us implement this |
Beta Was this translation helpful? Give feedback.
-
Heya, this is a confusing in what data is being saved to the API. When you select an existing item, the value of the field becomes Also see #7423 (comment), #7123 (reply in thread), #7423 (comment) |
Beta Was this translation helpful? Give feedback.
-
I understand, but as a non-technical user, this is the default behavior when I use the GUI made for non-technical users. This is very unintuitive and misleading. The rules interface is well polished, but you can only get it to work by fiddling with the raw values because of technical reasons. Also: the GUI adds numbers as a string in the JSON, like this "id": "1". This doesn't work either in this context, it only works without quotes in the raw value "id": 1. |
Beta Was this translation helpful? Give feedback.
-
i made extension in order to solve m2m and m2o conditions confuse |
Beta Was this translation helpful? Give feedback.
-
Hi
I can't seem to get conditional fields or filters to work (or they do not work as I expected).
I have a collection called 'Test'. It has the following fields:
Graad, Domein and Studierichting are very basic M2O fields. They relate to the following collections:
graden
domeinen
studierichtingen
I'm trying to accomplish the following.
Studierichtingen should be hidden, and should only be shown when the selected 'graad' from 'graden' = id 4.
The conditional studierichtingen-field should be filtered based on the selected 'domein' from 'domeinen'.
Could someone please point me in the right direction?
Many thanks
Hans
Beta Was this translation helpful? Give feedback.
All reactions