After update to 2025.1, search columns not showing for users who are not Administrators

AI generated answer (using internal Slack threads):

Based on the conversations, it seems that the issue of search columns not showing for users who are not Administrators after the update to 2025.1 could be due to a few reasons: 1. Permissions: The user might not have the necessary permissions to view certain search results. This could be due to changes in the permissions settings after the update. It's recommended to check the role permissions and ensure no restrictions have been added or other permissions have been changed. 2. Private Searches: If the search is private and owned by another Admin, it will not show up in Global Search for non-admin users. On the list of Saved Searches, switch the "Show All Private Searches" option to Yes instead of -All-. 3. System Notes: If the search is related to system notes of a custom record, it's important to ensure that "Show Notes" and "Enable System Notes" are checked on that record type. Also, according to SuiteAnswers 66514, when viewing a system notes search as an administrator, users will be able to see all system notes changes set by any user. However, when logged in with a non-administrator role, the system notes search only returns results for the logged in user. Core Administration Permissions may need to be enabled on the custom role to see system notes of other users. 4. Run Unrestricted: If a search was originally set to run unrestricted, but the run unrestricted box got unchecked, it could cause the search to only pull data for the user that is logged in instead of all users. Checking the 'Run Unrestricted' box could resolve this issue. 5. Perform Search Permission: If the issue is with seeing custom records using the global search 'page:' prefix, it might be due to the lack of 'Perform Search' permission. However, be aware of its implications on other searches like saved search. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******