I have two ui-select in my view. I want to disable some values in second ui-select with respect to first. That means when I change values to first, some of the values in second that are related to selected item in first, would be disabled.
If this is database-driven, is there a field which relates the data so as to be able to dynamically check values (e.g., types > subtypes)? If so, you can use ng-if="" to selectively load select items.
You would need some sort of relationship between the values to be able to programmatically (dynamically) perform the task. Otherwise, you'd have to manually do it.
Related
I am using episerver auto suggestion like this
https://world.episerver.com/documentation/Items/Developers-Guide/Episerver-CMS/9/Content/Properties/Property-types/Built-in-auto-suggestion-editor/
It works fine, what I want is to let the user add multiple value from the dropdown menu. Is it possible to do? I have seen the other way with the select multiple attribute, it creates checkbox and no auto suggestion is available.
No, there's no such option out-of-the-box.
The AutoSuggestSelection and SelectOne attributes result in dropdowns whereas the SelectMany attribute results in checkboxes.
Note however that AutoSuggestSelection doesn't force the user to select one of the suggested values, so it differs from the other two attributes.
There are others who wish for an equivalent attribute for select many scenarios, but your only option currently is to create a custom editor.
There seems to be a minor bug with the default dropdown filters when you enable filtering, is there a simpler way to force a table to use all input box style filters rather than to implement custom filters for each default drop down.
I think custom filters will solve the issue, but the problem is that doing so for the many tables will probably take far too long.
yes - you get dropdowns for fields where you are adding LOVs to.
But if you will create a duplication of the field (one attribute with LOV, a second attribute - without), you can show inside the table the-attribute-with-LOV, but in filter you will use the-attribute-without-LOV.
You will need to edit the jsff sources yourself.
I want to make react-select accept values which are not stored in the options array. I'm hoping to use this component to suggest values but also allow users to input their own value and persist it on blur.
In my situation the options represent suggestions which have been defined in the DB, on choosing an option it will auto-populate some other relevant fields.
However I also want to allow the user to define a unique value in the and manually define the other values.
I don't want to feed the unique value in the options array because I do not want the user to see this as a selectable option.
Is this possible with react-select?
If I understand your question correctly, you can totally control what's shown to the user as part of the selectable options, and also you have a dedicated class Select-create-option-placeholder attached to labels of new labels that need to be created (namely aren't part of the array of suggestions).
What's the best way to dynamically populate dropdown options in jqgrid advanced searching?
1) The first way: use "dataUrl" option of "searchoptions"
Disadvantage: when user add new criteria, and choose the attribute, dataUrl was posted to the server, when user add the same criteria again, dataUrl was posted to the server again, and with twice. very strange.
Advantage: the values user selected previously was there and not cleared.
2) The second way: use "dataInit" option of "searchoptions"
Disadvantage: the values user selected previously was cleared when adding new criteria(can not accepted, because it is not user-friendly, please refer url: the selected value was cleared in dropdown after add new criteria in jqgrid advanced searching)
Advantage: data was loaded into page when the page refreshed and only once.
3) the third way, use "value" option of "searchoptions"
but it's not dynamically, just hard-coded in page.
Could any one share the best practice about the issues. thanks.
I start with the second option. I suppose that you use dataInit in the wrong way. The goal of dataInit to initialize the control, like convert <select> to select2 or set jQuery UI Autocomplete or jQuery UI Datepicker on text input element. One should not fill the control with values. The select control is already created and filled before calling of dataInit.
If one use the first option, one can set HTTP cache header to prevent multiple request to dataUrl.
About the last option: one can set searchoptions.value dynamically inside of beforeProcessing for example. See the answer, this one and this one.
Folks,
I am using ng-grid to display a list of items.
I want to give my users ability to rearrange the rows in the list.
i.e move the rows up and down as they please.
Now,
However when I update the grid data in the backend i.e say change the index of a particular row, that row does not automatically change locations in the front-end.
What am i missing here ?
I have created a plunker to describe the problem
http://plnkr.co/edit/s1hrTSqF2zeZo3Btaln0
The grid doesn't use the index of the array to order it, so even if you are changing it, because the data is still there nothing happens.
What you could do is define an order field and update the value then changing the values as shown in this plukr. The order field you can hide it from the grid if required using columnDefs to explicitly defined which column should be shown.
Regards