Hi all we have a searched that has been working for years with no issues the looks at the system notes of a custom record. Something happen over the weekend that is causing the saved search to only pull data for the user that is logged instead of all the users. Has anyone run into something similar? This search still worked after our upgrade to 2024.2

I'm sure this is the already the case, but double check that "Show Notes" and "Enable System Notes" are checked on that record type. Only other thing I can think of is if you had some criteria that was running something like Set By "-My Team-" and then the supervisor hierarchy changed, or some other similar iteration where you had criteria that was pointing to something specific and something about the underlying data structure/hierarchy changed.

I checked all that and nothing changed i did find though this suiteanswers 66514 Scenario User is trying to determine the difference between the system notes search results for an administrator and a non-administrator role even when both roles have the notes permission level set to full. Solution 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. For more information, see 82465 Core Administration Permissions. Which doe snot make sense since this was working up until Monday

Interesting. Yeah, that doesn't jive with my experience either, but things change all the time, and it looks like that's only as of 2024.1, so 🤷‍♂️

Thanks for your help the run unrestricted fix my issue in the inetrim

Happy to help! Glad it's working. That means it's definitely some kind of permissions issue, and that core admin permissions thing you brought up definitely sounds like a likely culprit, although I hadn't heard of that before.

I think i found the issue they were originally set to run unrestricted but somehow the run unrestricted box got unchecked over the weekend since i did see a defect related to this last week. Thanks again for your help