Question

Can I Hide Specific Field Values Based Upon User?

Updated February 22, 2016

asked on August 22, 2014

Hello,

I feel fairly confident that there isn't a great solution to my issue other than what I already have in mind, but I'll be happy to find out if someone has a great solution for me, so here goes...

I have a client that is using a single template to file client documents. Per the screenshot, you will see that the first two fields of the template include 'Branch' and 'Client Name'. These are dynamic fields and pull from a SQL View that we've created.

The documents are filed away by branch, and we have access rights setup (by branch) so that end users can only see the branch that they work for.

The issue...

After further requirements analysis, even though we have the files locked down by branch, the template data is problematic in that they can see client names for other branches within the Client Name field

The question...

Is there some way that I can build in some conditional logic to say that if Employee A is a part of the Atlanta branch, that he only be able to set the branch field value to "Atlanta"? I'm not aware of anyway to do this and I'm thinking I may have to create individual templates per branch and individual SQL views per branch and then lock the templates down between the branches.

Any ideas would be appreciated!

Screenshot of Template.JPG (29.27 KB)

| Download

0 0

Replies

replied on August 25, 2014

I really don't think there's way to do this outside of templates for each branch. If it was just the files this would be a candidate for security tags but there isn't really any sort of equivalent when it comes to template/field security.

1 0

replied on August 25, 2014

Really, the only way might be to use Forms in conjunction with this process, only allowing changes to be made if one uses a form which is specific to the various steps they are in the midst of. This however does not sound like the type of solution you are hoping to make use of though as it would be a bit messy to do that transition to using forms.

Chris Hagen's idea of using several metadata fields is likely the way to handle this but would still be quite tricky, but not require extra learning from the user side.

0 0

replied on August 22, 2014

Hmm....do you have forms? maybe you use that? Otherwise it is not possible with the normal methods you are mentioning. it would definitely be a unique configuration to accomplish this

0 0

replied on February 22, 2016

Why not add in the template a field automatically filled with user name (using tokens) and then fillup the SQL View with a column (to filter on) with user names ?

0 0

You are not allowed to follow up in this post.

Question

Question

Can I Hide Specific Field Values Based Upon User?

Replies

Sign in to reply to this post.