Running as a user doesn't accurately reflect if a user can see constituent tabs with visibility expressions

When in Design mode and trying to use an expression to set visibility on a constituent tab, you might notice that running as a user does not accurately reflect whether the user can actually see the tab.
We are currently evaluating this issue for a fix in a future service pack.

Steps to Duplicate

1. Go to a constituent record
2. Go into Design mode
3. Click Edit tabs at the top of the page
4. Select the tab and you want to secure
5. Edit the visibility expression to add the following expression: = (not Globals.CurrentAppUserName = "DOMAIN\[Username]") andalso (not Globals.CurrentAppUserName = "DOMAIN\[Username]")
6. In the CurrentAppUserName expression, change the term DOMAIN to your Domain, and [USERNAME] to the username of someone who shouldn't have access to the tab.
7. Notice that when you run as that user, you can see the tab but when they log in they cannot see the tab.

Environment

 Blackbaud CRM
 4.0
 4.0.166.0

Was this article helpful?


Thanks for your feedback! Did this solve your issue?

Comments (optional):


Thanks for your feedback!
We're glad it was helpful but sorry it didn’t solve your issue. If you need assistance, click Chat with Support below.
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):


Thanks for your feedback! If you need assistance, click Chat with Support below.
Thanks for your feedback. Help us make our products even better by sharing details in our Idea Banks or our online Community.
Thanks for letting us know. We'll work on clarifying the information in the article. If you need assistance, click Chat with Support below.
Thanks for letting us know. We'll work on updating the search engine to return more relevant results.