There seems to be a behavior change in NetSuite re...
# general
s
There seems to be a behavior change in NetSuite related to saved searches configured to "Run Unrestricted" - Prior to 2025.1, if you added a result field from a joined record type (a record type which a user doesn't have permission to view), the value would show up in the search results. As of 2025.1, NetSuite seems to hide the result column entirely in this scenario. However, if you use a formula field, the value still shows in the results. There's conflicting information on what Run Unrestricted does (field help says, "Check this box to make search results available to users who normally do not have permissions to see the underlying records"), while SuiteAnswers says "The Run Unrestricted setting on saved searches does not supersede the record permissions set to the user's role. Unless the user has permission to the record type used for the search, running the saved search unrestricted will still not allow the user to view the search results." Anyone know what the expected behavior should be for joined fields? I'm seeing conflicting help information and conflicting results in 2025.1.
j
I can't speak to how 2025.1 is, we have a late release date and I haven't really gotten into it yet. However, I believe I can deconflict what the help is saying: My interpretation here is that running a search unrestricted should show all fields/results even ones a user doesn't have access to, but the permissions on the record type of a search are not overridden by this setting. An example: You have a custom field on the vendor record, that is restricted to a particular role. Now you run a vendor saved search and include that custom field and mark the Run Unrestricted checkbox. A user with a role without at least the Vendors (view) permission would NOT be able to run the search at all and thus would not see the search results. However, a user, who does have this permission, even if their role is not able to view that custom field, WILL see that field in the results in the saved search. As a corollary, I believe the expected behavior is that joins should generally show up with the Run Unrestricted checkbox as long as the user has permission to the primary record type for the saved search itself. I.e. permissions control whether or not you can actually run the search, but run unrestricted will show all the results assuming you can run the search. But who knows what support will say?
s
They just said it works as expected 🙂
Thanks for the detailed response
j
No problem. Yeah, that checks with my expectations 🙄. If you get them to commit to the fact that nothing has changed between 2024.2 and 2025.1, I can test the behavior later and confirm if I'm seeing the same in 2024.2.