{"section":"known-issues","requestedLocale":"en","requestedSlug":"case-variations-in-document-id-cause-duplications-in-indexer","locale":"en","slug":"case-variations-in-document-id-cause-duplications-in-indexer","path":"docs/en/known-issues/Storage/case-variations-in-document-id-cause-duplications-in-indexer.md","branch":"main","content":"## Summary\n\n\nWhen creating a document and then applying a patch request with the ID in a different case (e.g., all uppercase), the system treats it as a new entry in some components. This issue occurs because document persistence in database is case-insensitive, meaning only one document actually exists. However, other flows, such as the indexer, handle the ID without case normalization, leading to duplicate entries in the search API.\n\n\n#### Simulation\n\n\n\n1. Create a document with an ID in lowercase.\n2. Apply a patch request using the same ID but in uppercase (or any other case variation).\n3. Observe that the indexer creates multiple records for the same document ID, even though only one document exists in database.\n\n\n#### Workaround\n\n\nEnsure that all ID references use a consistent case before sending requests to avoid unintentional duplications in the indexer."}