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
------------------------------
Original Message:
Sent: 05-09-2022 11:49
From: BuildPro
Subject: Clean up Searchable fields - best practices
Is there a way to "uncheck all"? I have 2500+ fields in my Jobs Table. Very tedious to uncheck one-by-one.
Thank you
------------------------------
BuildPro
Original Message:
Sent: 02-01-2022 13:50
From: Evan Martinez
Subject: Clean up Searchable fields - best practices
Hi BuildPro,
One field type that can be very intensive is Multi-line text blocks. If you have sections where users might be entering paragraphs of text removing them from search can help avoid situations where people look for text strings against big blocks of text if that is not your intention. The same is true for any formula or relationship fields you have in your app that someone wouldn't want to search against. For example if you are using formula fields in the background for calculations that wouldn't need to be searched on reports or if you are using fields to style text you usually don't want to include both fields in a search as that is duplicative.
------------------------------
Evan Martinez
Original Message:
Sent: 01-31-2022 18:40
From: BuildPro
Subject: 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
------------------------------
BuildPro
------------------------------