Hi
I want Firebase to store 10 fields of data in a row or similar and there could be 1000 or more rows
Lets say
Make, Year, Model, Variant and 6 other bits of Info
There are many Makes with many combinations
In thunkable I need to create 4 drop down boxes where the user would enter a Make and Year of manufacture then Firebase returns in the third drop down, a list of Models, a Model is selected then firebase returns in the fourth drop down, a list of Variants.
Once there is a match in Firebase of the first 4 fields I want to return the other 6 fields in Firebase to a list
I am connected to firebase and have written a very simple save to Firebase using Join with Comma’s and Get from Firebase using a list and list from text to extract to a list
I dont want to store all this info in the phone or variables. Easier to update and manage all the combinations in Firebase…
Is Firebase able to offer this lookup type function and return more info based on a match
My intention is to enter many many rows of data for each vehicle brand and return some very specific data if Make Model Variant and Year match
Once the Make Model Year and Variant match what I have already entered into Firebase or Airtable, then other fields are returned to Thunkable App and need to display in with a label and the data. Example Colour - White. Colour being a label and White being the data
Example
1.Entering Jeep in the first drop down would then load the relevant options in the second drop down
2. Options in next drop down might be - Grand Cherokee, Cherokee, Blackhawk
3. Options in next drop down might be - 2014, 2015
4. Options in next drop down might be - Petrol or Diesel
Once the match has been made with the above data then I want to return other information about the vehicle, another 6 fields of info
First of all, Firebase is catered for large volume and you can easily store and retrieve hundred of thousands of records with ease and relatively good speed.
Due to the fact that Firebase is JSON based and not relational SQL type of database, the data structure model is a bit different and for sake of speed you will need to allow duplication of data.
I will create a data node just to fill search fields and that is mainly for performance issues.
The actual vehicles data will reside in a separate data node that can be looked up by the set of search fields presented. Under the vehicle data node I will create sub-nodes for each Make which will give me a performance advantage in searching for matched results.
If I would build such an app, I would start structuring my DB with the following
Common App Settings
This is to manage info in the app in a dynamic way.
Look up tables/lists
For performance issues, I will have the information for the user choices and options in a separate key for the app to retrieve faster.
Actual vehicle info
This is the main bucket which will hold the major part of the info and is already separated by vehicle type again for performance purposes.
Of course this is only a start, as far as I understood of the case, and the more you get into the app itself you might need to add and go deeper in the node tree.
HI Muneer
I have spent hours reading threads on the community and having trouble getting my head around filtering data from FB. I am having trouble understanding the filtering and am in over my depth here…
I was going to have 5 lists to get the first 5 pieces of information.
Make, Model, Variant, Year, Fuel Type. Depending on what is selected then it will follow that NODE.
The length of the text between each set of brackets will vary so I cant see how I can use Letter to Letter for the substring
I have managed to have a list retrieving the first node when screen starts (Kia)
