After enabling Dataverse Search, certain fields are newly available and automatically selected for the entity. If we remove these fields from indexing, will there be any impact?
Yes, removing fields from the Dataverse Search index does have direct impacts because search relies on a separate indexed store.
Key Impacts 1. Search & Discovery Limitations
Users cannot search using data from removed fields
Example: If City is removed, searching “Seattle” won’t return results unless it exists in another indexed field
Removed fields will not appear in search results (views, filters, snippets)
2. Copilot / AI Impact
Reduced AI context
Copilot or generative AI features cannot use data from unindexed fields, leading to less accurate or incomplete responses
3. Storage & Performance Benefits
Reduced storage usage (less duplicated data in the search index)
Improves efficiency, especially when removing large text fields (e.g., descriptions, emails)
4. Technical & Capacity Benefits
Frees up column/index capacity limits in Dataverse Search
Allows indexing of more important business-critical fields
Best practice: Keep only high-value, searchable fields in the index and remove unused or noisy fields after proper validation.
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.