Why Indexing Configuration Affects Document Retrieval Speed
When finance teams search for supplier invoices or compliance officers retrieve audit documents, retrieval speed depends on how the system indexes content. Poorly configured document management system indexing can lead to slow searches, server delays, or incomplete results. Onfinity ERP maintains a separate index database designed specifically for document search operations, keeping these queries isolated from core transactional processes.
The DMS indexing settings window provides direct control over how documents are processed, how many records are handled per batch, and what minimum character length applies to search queries. These settings influence whether a search returns results in seconds or minutes, and whether bulk uploads complete smoothly or strain server resources.
How the Index Database Works Separately from Core ERP Data
Onfinity ERP stores document metadata in a dedicated index database, separate from purchase orders, invoices, and payroll records. This design prevents document searches from competing with transaction processing for database resources.
The index DB name field displays the name of this database. This value is informational and should not be changed. The system automatically creates index records as documents are uploaded and processed by the server scheduler. When a user searches for a contract or receipt, the query runs against this index database rather than the main ERP tables.
Setting Document Upload and Indexing Batch Sizes
Two fields control how many documents the server processes at once. The first, labeled “document upload in one time per user,” determines the batch size for upload processing. The default value is 100 documents per cycle.
The second field, “index record in one time,” sets how many documents are indexed during each processing run. This also defaults to 100 records. Both settings work with auto-upload configurations to automate document ingestion from network folders or email attachments.
Increasing these batch sizes speeds up bulk processing but requires more server memory and CPU capacity. Organizations with high document volumes may raise these values to 200 or 300, while smaller teams may reduce them to 50 to balance workload. These adjustments affect how quickly uploaded documents become searchable in the system.
Controlling Search Precision with Character Length Settings
The “index based on character” field defines the minimum character length for both indexing and searching. The default value is 2 characters, meaning the system indexes two-character combinations and requires at least two characters in search queries.
This prevents single-character searches that would return excessive irrelevant results. A search for “A” would otherwise match thousands of documents. Setting the minimum to 2 or 3 characters improves precision and reduces processing time for large repositories.
Organizations managing technical documents with many abbreviations may keep this value at 2. Teams working primarily with full-text contracts or reports might increase it to 3 to narrow search results and reduce index size. This setting directly affects how users frame search queries and how quickly results appear.
Managing Upload Logs and Image Text Extraction
Onfinity ERP tracks document processing activity in upload history logs. These logs record when each document was uploaded, whether processing succeeded, and any error messages if issues occurred. The “number of days to keep log” field controls automatic log cleanup to prevent database bloat. The default retention period is 7 days.
Setting this value to zero disables automatic deletion, retaining logs indefinitely for audit or compliance purposes. Finance and legal departments with strict record-keeping requirements may choose permanent retention, while operations teams focused on recent activity can keep the default weekly cleanup.
The “read image” setting enables text extraction from image-based documents. When activated, the system processes scanned invoices, receipts, or signed contracts to extract readable text. This makes image files searchable within the DMS, allowing users to find a scanned vendor invoice by searching for the vendor name or invoice number embedded in the image.
Image processing requires additional server resources but significantly improves searchability for organizations that receive paper documents or email attachments as scanned images. Accounts payable teams benefit from this feature when managing supplier documentation that arrives in mixed formats.
Applying Indexing Settings to Your Document Workflow
Onfinity ERP ships with default indexing values optimized for typical enterprise document volumes. Super user accounts with system administrator roles can modify these settings through the DMS database configuration window. The “record type” field indicates that these settings are user-maintained and will not be overwritten during system updates.
Changes should be tested in staging environments before applying to production systems. Adjusting batch sizes affects how quickly uploaded documents become searchable. Modifying character length settings changes how users search and what results they see. Image processing activation increases server workload but improves retrieval for scanned documents.
Properly configured indexing improves document findability for purchasing teams searching supplier contracts, accounting staff retrieving invoice backups, HR departments managing employee files, and legal teams accessing compliance records. The settings balance processing speed, search accuracy, and server resource usage based on organizational document volume and search patterns.
See These Settings in Your Environment
If your team experiences slow document searches or unclear upload processing behavior, review your DMS indexing configuration. Onfinity ERP provides direct access to batch size controls, character length settings, and log retention options that influence both search speed and server performance. Request a demo to explore these settings in a live environment and see how they apply to your document workflows.
Follow us on our LinkedIn page for updates and insights.