Text Search Group ignored with exact match not working when different tables have same prefixDescriptionThe exact match is confused when there are records in the sys_number table that have the same prefix. When there are exact match records in more tables, the search results will return records mixed across the tables, not honouring the Text Search Group.Steps to Reproduce 1. Create a record in both tables "issue" and [pm_portfolio_issue], giving the same number "ISU0010001".2. Go to "System definition" - "Search Groups".3. Open the "Tasks" record and add into search group "Task" the two entries "issue" (number 800), and "pm_portfolio_issue" (number 900).4. Search "ISU0010001" in global search group. This will show "Exact Match" for one of the records randomly, though there are two records matching, failing the complete search.WorkaroundAfter carefully considering the severity and frequency of the issue, and the cost and risk of attempting a fix, it has been decided to not address this issue in any current or near future releases. We do not make this decision lightly, and we apologise for any inconvenience. The workaround is to ensure that the prefix for records in sys_number table are unique for each table.NOTE: If changing the prefix of an already populated table, the auto numbering using the new prefix applies only for the new records, all pre-existing records will still have the old prefix.The auto record numbering is documented here:https://docs.servicenow.com/bundle/rome-platform-administration/page/administer/field-administration/concept/c_ManagingRecordNumbering.htmlRelated Problem: PRB1239650