One of the user doesn't see the "save" button on t...
# administration
n
One of the user doesn't see the "save" button on the saved search. Why? I have given them Perform Search and Publish Search permissions.
c
Who owns it? Is allow users to edit set on it?
n
He is creating it.
He can "submit" it to run and show results... but there is no Save button.
c
Download the permissions excel spreadsheet from help/suiteanswers and search for it
n
search for what?
Downloaded the sheet.
c
Saved search
s
permission = publish search
n
I have added that permission
k
publish search shouldn't have that impact - it only allows them to check the public checkbox
make sure perform search is full, and not view
if there is a "run unrestricted" checkbox on the search the user is trying to edit checked - they shouldn't be able to save it
user also needs to be sure to log out and back in after edit on their role
n
Log out and log back in - done.
User is trying to create the saved search. Not edit any existing one.
Perform Search is Full.
k
What's the record type they are trying it on?
Side note - it is very possible for roles to get bugged when assigned to users. It's not frequent - so if someone else with the same role can create/save searches, I'd try removing it from the user and adding it back.
n
I tried assigning that role to me. Same issue.
Transaction record. JE.
k
I presume they have the "find transaction" permission?
not that it should cause the behavior... but stretching for ideas
c
Permissions are up there when considering the worst bits of NetSuite
k
I don't generally have too much heartache with it.
But this is an oddball one for sure
n
It sure is.
The search works. It shows the results. But the user doesn't see the save button. Only Preview.
r
have you done a screenshare with the user? to make sure she is not just missing something?
n
I did. I even assigned the role to myself. Same issue.
k
I would be tempted to remove the perform search permission - save it. Log in and see if it goes away completely - then re-add the perform search permission to the role to see if that fixes it
otherwise - I'm probably just spinning up a new role from scratch
n
Perform Search permission was not there when the issue occurred. I added it hoping to remedy the problem. But it didn't work.