-
Created by
Karina Gilmanova, last updated on 14 Sept, 2026
3 minute read
User Question
Search does not work out correctly immediately after creation a new master data object
Problem / Symptom
Completely unsearchable object. Newly created object to be completely unsearchable right after creation—not just deprioritized, but entirely absent from the search results.
Partial match instead of exact. The substring search for example “test” triggers against already indexed descriptions, for example "Test lead-CAT"
Visual mismatch. The user can see the sought-after item in the overall list (after scrolling), but not in the filtered results—hence the perception that the search is malfunctioning.
Conditions
The issue appears immediately after creation a new master data object (item, warehouse, employee, bank, document and etc.).
The issue appears in searching either in the the list of documents or inside the document itself.
The issue reproducible only within the first 15 minutes after creation/modification.
Root Cause
The full-text search mechanism in the FirstBit platform operates asynchronously. When a new object is created, the data is saved to the main database instantly, but it is not immediately added to the full-text search index. The index update is handled by a separate background process (a scheduled job).
Diagnostics
Check the full-text search index status.
1. Go to Administration > Full-Text Search Management:
2. Click on Clear Index > Update Index:
Or run the background job schedule manually.
1.Go to Administration →Scheduled and Background Jobs.
2. Find the job named Full-Text Search Index updating:
3. Click on Execute Now button:
Resolution
1.Update the full-text search index or
2.Run the background job schedule manually.
Related Materials
Product / Configuration
FirstBit ERP/FirstBit Accounting/FirstBit Contracting
Functional Area / FirstBit Software Section
Administration, master data.
Thank you for being FirstBit customer!