{"section":"known-issues","requestedLocale":"en","requestedSlug":"crm-ui-relationship-field-search-fails-when-related-field-is-auto-increment","locale":"en","slug":"crm-ui-relationship-field-search-fails-when-related-field-is-auto-increment","path":"docs/en/known-issues/Storage/crm-ui-relationship-field-search-fails-when-related-field-is-auto-increment.md","branch":"main","content":"## Summary\n\nIn Master Data v1 CRM UI, relationship fields that display a related entity’s Auto Increment field fail to load autocomplete options. The UI issues a DynamicForm/LoadAutocompleteValues request that uses wildcards, but Auto Increment fields are indexed as long (numeric), which do not support wildcard operations, resulting in an “invalid filter” and blocking edits in the relationship field.\n\n## Simulation\n\n- Prerequisites:\n  - Master Data v1 with a relationship field in entity A pointing to entity B.\n  - The relationship’s “Related field to display” in entity B is an Auto Increment field.\n- Steps:\n  - Open the CRM UI form that contains the relationship field.\n  - Type partial characters to search for a related record (this triggers autocomplete).\n  - Observe the backend request:\n    - GET DynamicForm/LoadAutocompleteValues with containsExpression (wildcards).\n  - Result:\n    - The request returns “invalid filter” and the UI cannot list/select related records for the field.\n\n## Workaround\n\n- Edit the relationship value via API instead of the CRM UI while this limitation exists.\n- If possible in the customer’s data model, change the relationship’s “Related field to display” to a string field (e.g., email, name, external code) that supports text search/wildcards in autocomplete."}