Clean up Searchable fields - best practices
Hello, I would like to clean up my searchable fields, assuming this will improve QBASE performance. Any suggestions on what field types definitely don't need to be searchable? thx -------------...
Forum Discussion
I'm late to the conversation here (was looking for a discussion on whether making lookup fields searchable or not has an impact on performance) but you can do this with the the Quickbase API and pipelines. I am once again shouting out Scott Galloway and his Empower session from last year (https://youtu.be/6gAHfV0PDWk) in this solution. You would have one pipeline call another pipeline, and that second pipeline would loop on itself calling this endpoint, https://api.quickbase.com/v1/fields/{fieldId}?tableId={tableId} first to see if the field exists, and if it does then you would call this endpoint, https://api.quickbase.com/v1/fields/{fieldId}?tableId={tableId} and in the payload have "findEnabled": false. Whether the field exists or not you would loop the pipeline back on itself adding 1 to the field ID each time. Scott's video describes how you can make sure to limit the number of runs that occur only to the number of fields you have based off the field ID number.
------------------------------
Daniel Johnson
------------------------------
------------------------------
Daniel Johnson
------------------------------
https://developer.quickbase.com/operation/updateField
------------------------------
Daniel Johnson
------------------------------
------------------------------
Daniel Johnson
------------------------------
- Actually, you might start by using the JSON handler and calling https://api.quickbase.com/v1/fields?tableId={tableId} first, because then the JSON handler will setup the loop for each field ID, so you wont' have to do that part yourself.
------------------------------
Daniel Johnson
------------------------------