Search functionality not working on 1 table only
Search bar should be there but it’s not
Search bar being there
Hello @ed.sparks,
The global search bar should be shown unless it has been deactivated by a customization, or if it is a smart collection, which is not searchable by default.
Did the search use to be working well for this collection at some point ? If so when did start to see that the bar disappear ? Does filtering work correctly ?
Please let me know on which collection does the problem occur 
Hi Nicolas,
It’s a normal collection with 1 smart action but we haven’t made any changes to it.
Where would we be able to turn it off. I haven’t been able to locate something like that?
And yes, it’s been working for a few years and never been an issue.
what is the collection name please ?
I have found 1 collection that is not searchable in your api schema, the collection “Campaign”. Is that the one ?
Hi Nicolas,
Yes, that is the table. But we haven’t made any changes on our side that would have affected that to my knowledge.
Ok. Indeed, looking through your apimap versions (since 09/09/2024), it has always been this way.
Maybe we fixed a bug which previously let the search bar appear on frontend in this case, but I’m not aware of any.
In any case, you will have to update your agent schema or customization to try and enable search on this collection, since it is the expected behaviour from frontend side.
Hi Nicolas,
Thank you for finding this.
We haven’t got anywhere in our codebase where we have deactivated the search.
The only addition we have made to this table is we created a new field in the collection as Forest Admin would not display one of our fields correctly and I spent time with the support team on a call writing the workaround. Which is here
class ForestLiana::Collections::Campaign
include ForestLiana::Collection
collection :Campaign
search_code =
lambda do |query, search|
# Injects your new filter into the WHERE clause.
query.where_clause.send(:predicates)[0] << " OR (campaign_id = '#{search}')"
query
end
set_code =
lambda do |user_params, code|
user_params[:campaign_id] = code
user_params
end
field :campaign_code, type: 'String', search: search_code, set: set_code do
object.campaign_id
end
action 'Import Campaign'
end
Outside of this, there is a smart action “Import Campaign”
class Forest::CampaignsController < ForestLiana::SmartActionsController
# Smart Action for importing campaigns directly from the Forest Admin dashboard
# This action is triggered when the user clicks on the "Import Campaign" button
def import_campaign
campaign_id = ForestLiana::ResourcesGetter.get_ids_from_request(params, forest_user).first
user = User.find_by(email: forest_user['email'])
Campaign.find(campaign_id).init_import(user) if user
head(:no_content)
end
end
Outside of this, where would I re-enable the search functionality or override the schema?
Hello @ed.sparks,
I have reproduced the problem on my side.
You can add the is_searchable: true option to force the collection to be searchable, as shown below:
class ForestLiana::Collections::Campaign
include ForestLiana::Collection
collection :Campaign, is_searchable: true
I have been told that indeed, we fixed a bug with the search bar recently. Sorry for the inconvenience caused 
Thank you for looking into this Nicolas.
I’all add the change now.
Many thanks
Ed