Hello @Anonymous ,
The issue isn’t related to field caching or mappings. Instead, it’s about keeping the AI Search index structure consistent over time. Once an index is created, most field definitions (except for "Retrievable") are locked in and cannot be changed. Adding new fields is possible, but modifying existing ones requires rebuilding the index.
Because of this, developers often use the Azure portal for quick tests and simple index setups. However, for frequent changes or iterations, a code-based approach is recommended, as it allows you to rebuild the index more efficiently.
- Do I need to reset or delete the indexer before the new fields appear? → Yes, you need to rebuild the index.
- Can I force Azure Search to update only the new fields? → No, new fields must follow the original index schema.
- Could this be caused by indexer caching or field mappings? → No, that’s not the issue.
You can refer to the Azure Search documentation for more details.
Hope this helps!
If you found this answer helpful, please click Accept Answer and consider upvoting it /click yes.
If you have any further questions, please click Comment.