super weird one today. A particular user in a par...
# suiteanalytics
j
super weird one today. A particular user in a particular role gets “A User Error Has Occurred Search error: Parentheses are unbalanced.” on a search. Myself in same role, fine. Her, other role, fine.
k
I'm betting it's a permissions issue. I'd look at the differences between the roles.
And what the formula is using.
j
it’s not the role, I tested it using the same role (I don’t have global permissions)
besides, if it’s permissions, wouldn’t it give a permissions error (or just not return the results)?
k
Of you own a list a field is created on you might get visibility to it even on a role that doesn't have access to lists.
A better test would be to have another regular user attempt to run the search
j
It’s just a list of support cases though — and it works for her in a different (lesser) role so I don’t think it’s an ownership thing.
n
Are you viewing the same page?
k
Is it an issue when viewing the list, or a specific search?
n
I had the same error message was set up for a view for I believe it was for work orders
because one of the properties wasn't available for the view, it omitted that line in the view's saved search criteria, which included the paren
Viewing the transaction list
Further complicating it, because the view didn't run properly, it didn't show up on the "Last Run Search" list, so I had to go line by line on the views available
k
Yeah - so this often happens when you screwed a search up and have it set as the view. Or if a role doesn't have access to a field that's part of search criteria
n
Yup. My steps would be go through the list views available and narrow it down to those with parens; you'll likely only have one or two candidates from there
k
There is a process for resetting the view to the default - there's something in Suite Answers for that.
n
True. That might be better to get moving again. I assume they still want to be able to use that view and determine the permissions they may need to grant
or change the criteria or filters to accommodate that
j
It’s just super weird that it’s happening only for her in that role….. in her other role (which has lower permissions) it works fine. She gets the error both in Dashboard view and if she loads the search directly.
OMFG
one of the 14 custom fields used in search criteria randomly had a permission set
k
Well, at least I pointed you in the right direction?
j
yup
I guess it worked for me as “owner” of the custom field…? no idea. Anyhow, error message was epically unhelpful
k
Yes. As owner of a custom field/list you will often get behavior that acts as though you have the permission - even when you don't so when you go to compare, it won't break like it does for users. Which is often why I set up additional logins to test, or have someone else test with me.