Answers.Body: <p>This should actually happen automatically. After saving an entry a queue task is created which updates the search index.</p>
  <p>You could verify if this also applies to other fields (especially text fields) and then file an issue at Craft‘s GitHub page. Maybe this is a bug for dropdowns only.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-05-08T14:06:57.847Z
Answers.LastActivityDate: 2022-05-08T14:06:57.847Z
Answers.UserDisplayName: Matthias Redl-Mann
Body: <p>I have a multiselect drop-down for age group and I have set &quot;Use this field’s values as search keywords&quot; check box  checked.
  when I create a new entry or update existing entry . we are not able to search using this field value unless we run this CLI command &quot;php craft resave/entries --update-search-index&quot;
  we don't want to run this command every time when someone create or update entry.
  Is there a solution to update search index automatically when someone create or update entry.</p>
  <p>Thanks,</p>
  <p>Amar Chand Yadav</p>
  
Tags: <entries><search><index><cli>
Title: Update Search Index on Entry create and update
ThreadText: # Update Search Index on Entry create and update
  
  (Asked by: username_0 on 2022-05-07)
  
  I have a multiselect drop-down for age group and I have set "Use this field’s values as search keywords" check box checked.
  when I create a new entry or update existing entry . we are not able to search using this field value unless we run this CLI command "php craft resave/entries --update-search-index"
  we don't want to run this command every time when someone create or update entry.
  Is there a solution to update search index automatically when someone create or update entry.
  
  Thanks,
  
  username_0
  
  **Tags:** entries, search, index, cli
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2022-05-08. Score: 1
  
  This should actually happen automatically. After saving an entry a queue task is created which updates the search index.
  
  You could verify if this also applies to other fields (especially text fields) and then file an issue at Craft‘s GitHub page. Maybe this is a bug for dropdowns only.
  
  
  ---
  
  