You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 3, 2024. It is now read-only.
If a new data value kind is created that allows the content editor to pick a class that implements a particular interface, they can have any function they want that returns a list of strings that can then be used to populate the data values for a drop down. They could do anything they want in that function, such as query a database or make a call to a web service.
In the process of implementing this data value kind, I should also make the drop down use data value kinds in a more generic manner. Right now, the drop down is hardcoded to recognize only the DataValueList data value kind. There should be some interface that new data value kinds can implement so that the drop down list can extract the necessary data from any data value kind implementing that interface (rather than restricting it to a single implementation).
A nice to have would be to also allow for different labels and values for each item in the list (in case the items in the drop down differ from the value that should be sent to the server).
The text was updated successfully, but these errors were encountered:
See this forum post: https://our.umbraco.org/projects/backoffice-extensions/formulate/formulate-questions/79575-customize-data-value-section
If a new data value kind is created that allows the content editor to pick a class that implements a particular interface, they can have any function they want that returns a list of strings that can then be used to populate the data values for a drop down. They could do anything they want in that function, such as query a database or make a call to a web service.
In the process of implementing this data value kind, I should also make the drop down use data value kinds in a more generic manner. Right now, the drop down is hardcoded to recognize only the
DataValueList
data value kind. There should be some interface that new data value kinds can implement so that the drop down list can extract the necessary data from any data value kind implementing that interface (rather than restricting it to a single implementation).A nice to have would be to also allow for different labels and values for each item in the list (in case the items in the drop down differ from the value that should be sent to the server).
The text was updated successfully, but these errors were encountered: