I've managed to create a small application that has a query based on the users input. It then accesses an API and pulls the data I need.
I then want to create a form (made from drop down menus) that is filled out based on the data query - the user then will be able to confirm the information is correct and if not change it to the correct option.
I don't know:
a) how to set up a drop down menu to have a variable default value
b) How to link the collected data to a key as there are a lot of variables that will point to the same drop down menu for example 1a,1b,1c,1d = Green, 2a,2b,2c,2d = Red, 3a,3b,3c,3d = Blue... Would this be something along the lines of creating a Key Index?
Thanks in advance for any help - not really been sure what to google with this problem.
Thanks for your help in regards to point 1, I suppose making a table of potential answers for the drop down helps this rather than manually inputting them.
This is the data I am collecting when a user runs a query.
I would then like to run this data into a form with drop down menus for confirmation, however there are multiple options within the data for what can be one drop down menu for us to collect instead. For example there are over 30 different entries for saying Loft insulation where I need about 4 options being : Limited Insulation, No Insulation, Full Insulation and another property above.
Hope that make it a bit clearer on what I'm doing.
I think I kinda get what you're after, but not totally certain. It sounds like you might need a transformer between your query and setting a default for the dropdown menu. That way you can condense your 30 input options to 4 output options.
In this test app, I'm using table1.selectedRow.data.userId as a proxy for your "30 options". Based on what that option is I used a switch statement to pick one of 3 menu options. Then I set the output of the transformer as the default value for the select input.
Instead of having the case fixed in the code is it possible to reference a table that has the different options? I've got 200 different value to be checking against and they might change at some point so it would be good if I could use a table that could be changed as and when instead of having a direct reference.
So, in your query you want to select all values for "roof-description"?
What does that query result look like?
And are you storing "cavity" values in another table in the database?
There is definitely a way this can be done by getting your data all at once and not having to run so much logic on the front-end
It's a little difficult for me to clearly understand what you want this app to do...but I'll take a stab
A user is entering information about a property. Based on the property you would populate the preset information you already have in your database.
So, for example select all options for the roof, cavity, heating, etc... each of these would need to be a separate query to populate the dropdowns so that the user could make the change if what you have assumed doesn't match what they have. Your assumption for each dropdown would be in the Default value for the dropdown.
The mapped value for each dropdown would be the name and id of each of the options for let's say roof...
select * from roof where property = 'Clementine Beach' this would give you group of values that contain the ID in the db and the description ("Pitched, 75 mm loft insulation")
You would get all of the ids for that record and its description and that is what would populate the description dropdown.
You would do the same from all dropdowns based on the property....
Or maybe I am way off and just don't understand the architecture you're looking for....but happy to continue to help.
OK makes sense. I would just get the data into a DB first and make sure that you have all the data you need related to the appropriate tables and then work on one query at a time. And slowly build out the form so that the data is simply populated in all of the drop downs. Then start building queries where your assumptions can be added to each default value of the drop down itself.
Eventually you'll add queries to insert the customer changes to another table or update to your "assumption" table....
I have found that by just focusing on the laying the groundwork (Pun sort of intended) it makes it easier to go back and start making more complex queries and chaining queries together as well. It also makes for a more challenging but fun learning experience. Let me know if there is anything else I can do to assist. Or just keep on posting as you need to as the people in this forum are always willing to lend a hand...best of luck and keep plugging away; you will get there.