{"section":"known-issues","requestedLocale":"en","requestedSlug":"searching-not-return-document-when-the-value-contains-a-plus-symbol","locale":"en","slug":"searching-not-return-document-when-the-value-contains-a-plus-symbol","path":"docs/en/known-issues/Storage/searching-not-return-document-when-the-value-contains-a-plus-symbol.md","branch":"main","content":"## Summary\n\n\nWhen searching for a document using a field value that includes the \"+\" symbol, the search does not return the document. This happens because the \"+\" symbol is incorrectly interpreted, resulting in the search value not matching the existing value.\n_This issue happens both in the API and in the CRM_\n\n\n##\n\n## Simulation\n\n\n\n1. Use the search API to query a field that includes a \"+\" symbol.\n2. The search will return an empty array. Example:\n\n    https://\\{accountName\\}.environment.com.br/api/dataentities/\\{entity\\}/search?_where=homePhone=+5512345678901&_fields=id,userId,email,homePhone,firstName\n\n\nIn CRM UI:\nIf you search for an email that contains the symbol \"+\" an error will be returned.\n\n    An unexpected error has occurred. Please try again. If the problem persists, contact support.\n\n\n\n##\n\n## Workaround\n\n\nThere are two ways to handle this issue:\nEncode the \"+\" symbol to \"%2B\", so the search query becomes:\n\n    https://\\{accountName\\}.environment.com.br/api/dataentities/\\{entity\\}/search?_where=homePhone=%2B5512345678901&_fields=id,userId,email,homePhone,firstName\n\n\nUse the \"*\" symbol as a wildcard, which will allow the search to match any character(s) before the specified value:\n\n    https://\\{accountName\\}.environment.com.br/api/dataentities/\\{entity\\}/search?_where=homePhone=*12345678901&_fields=id,userId,email,homePhone,firstName\n\nThis issue arises when searching for documents using field values that include the \"+\" symbol. The search API does not correctly interpret the \"+\" symbol, causing the search to fail by not matching the existing values. This problem is not limited to the \"homePhone\" field but can occur with other fields like email that might include special characters.\nTo work around this issue, you can either encode the \"+\" symbol as \"%2B\" in the search query or use the \"*\" symbol as a wildcard to ensure the search retrieves the correct documents."}