I need to create a form in which the fields are dynamically generated from the database api. The problem is that I have cases where I will have two selection fields, and one depends on the other.
For example:
Selection A - Manufacturer,
Selection B - Models
The Models that should be shown in selection B must only be the models of the manufacturer choosen in selection A.
As the form is made dynamically I don't have fixed states where I can check the value of selection A.
Does anyone have any idea how I could solve this problem?
Thanks,
Put an onChange handle on the Selection A (Manufacturer) in order to get the Selection B (Models) mounted based on the selected manufacturer.
Maybe you can fetch the models just after Selection A had a value selected.
Or, if you got all the models in the same moment when the manufacturers are fetched, when manufacturer will be selected you could filter models using it as reference.
I found the aswer and is very simple on my case, I'm using react-hook-form, so I only need use the watch function to see the valeu of
selection A, passing the name id of the component.
Related
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).
This may be a simple quesiton but I need to ask to be sure I am in the correct direction. In the Item Fulfillment form for example, there is a first column Fulfill that is a checkbox. Above it there are buttons for Mark All and Unmark All as well. What I would like to do is have similar functionality on one of my other subtabs. I already have a custom child record that lives on my subtab and added a checkbox bool field to the record. I could get that to somewhat work but what I would like to know is
1- is that the correct approach.
2- does it need to be a field that is selected to be saved,
3- for their functionality this only appears in Edit mode. is that a limitation?
4- I notice their "checkbox field" is not as wide as the one I made
5- Is there a way that I would only get this "field" to appear in the record when it is in a sublist and not when it is in its own custom form to create a new item? I would only have it as a checkbox in a subtab.
Or is my approach wrong and perhaps there is an easier way to do it?
Thanks
1 - You can create a check box using inline HTML field - script the check box that way. Call a client script's function to handle the click.
2 - Not really sure what you're talking about - if you mean "Store Value" in the field definition, the answer is "No".
3 - Edit mode, yes. You can't change values of a field when not in edit mode.
4 - Width of a field can be controlled on the form design.
5 - Create 2 different forms. The data entry form would not include the check box, the sublist form would.
I have a requirement to create a custom form field that is basically an extjs grid. The user should be able to click a result in the grid. This clicked result should then become the fields value. Also, this field needs to extend Ext.form.field. Here's what I got:
Ext.define('MyApp.field.Grid', {
alias: 'widget.GriedField',
extend: 'Ext.form.field.Base',
I'm a lot of confused on how to add a grid to form field base. Looks like form field base's template expects HTML. How do I get it accept a component?
If you just need to select a value from a list of items. Why not use a combobox?
If you need to select multiple items. There is an example of how to use the MultiSelect ux component in the documentation examples.
http://docs.sencha.com/ext-js/4-1/#!/example/multiselect/multiselect-demo.html
If you really must use a grid. Then I wouldn't bother with trying to create a field type and cause yourself grief.
Add a listener to your grids selectionchange event and update a hidden field in your form with the value you want from the grid. Job done.
I ended up putting the grid on a form indirectly through creation of dependencies on my model.
My model has master-detail, which the detail is just a store reference. I found that using associations did not work for me.
So, in adding a field to a form, I have something that manages changed events for the model (master record) and the detail stores.
I have following requirement.
Display data in a table
Clicking on checkbox filter out currently displayed rows by some condition
Clicking on checkbox once again return data appearance to it's previous state
To achieve this I've ovverided method rowQualifies in my ViewObject which is simple SQL based view object to apply my custom filter logic.
When user clicks on checkbox I refresh view object data to apply filter
viewObject.setDoFiltering(true);
viewObject.setQueryMode(ViewObject.QUERY_MODE_SCAN_VIEW_ROWS);
viewObject.executeQuery();
It works perfectly, data set updates without interacting with database and my custom filter logic applies as well.
But when I need to cancel filter it wouldn't work because iterator doesn't contain anymore previous rows, and I can only load them from database but it means that I can lose my changes already made to view object rows.
So, when I do
viewObject.setDoFiltering(false);
viewObject.setQueryMode(ViewObject.QUERY_MODE_SCAN_VIEW_ROWS);
viewObject.executeQuery();
It will return me those rows that were displayed previous time.
If I do
viewObject.setDoFiltering(true);
viewObject.setQueryMode(ViewObject.QUERY_MODE_SCAN_DATABASE_TABLES);
viewObject.executeQuery();
It will return me all rows, but I will lost my changes already made to view object rows.
My questions is how to avoid it? Maybe there is another way of doing this? Maybe it is possible to do something with RichTable to tell it how to filter rows in memory.
Any advices are warmly appricated!
I believe this can be done using ViewCriteria, to filter means to apply a ViewCriteria, and then disable it to view all your data