You are viewing limited content. For full access, please sign in.

Question

Question

If I have a dynamic field that shows the email address based on another field, Will setting security to be uneditable by normal users still allow it to show the only option?

asked on December 12, 2013

 I was setting up a template to use dynamic fields and it references a DB to get names, and when you select a name, it automatically fills in the metadata field with the only email address it will find (1 email address per person). 

 

We do not want to have the dropdown option as it is unnecessary, so I was wondering if since it automatically chooses the only option, if we remove rights to change the field from all users, if when they change the parent field to a person, if that dynamic field will show up with the proper e-mail address or will it remain blank?

1 0

Answer

SELECTED ANSWER
replied on December 12, 2013 Show version history

I don't think it will populate in that case.

 

The client actually loads the entire list and populates the drop down choices. It's still the "end user" who is effectively filling in the field even though the client is partially automating that function. In fact I've run into an little known "issue" where there is a maximum of 9999 choices in that list.

 

The better question is do they need to be able to see the email before they save it? If not you could have workflow fill in the field for you after saving. Since there's never a choice an end user has to make why make them do anything at all?

 

 

Interesting little known fact: The dynamic field list has a limit of 10k entries in any one drop down. We had a client who absolutely insisted on all 18000 entries be in one list so she could type ahead. We showed her the responsiveness when it was at it's limit (responsiveness was totally dependent on how fast your client can download and how fast it can display that many entries) and she quickly decided that our suggestion for typing the first letter, tabbing, then typing part of the whole name worked much faster in total. 

1 0
replied on December 12, 2013

I guess this will do. I can have workflow ensure that the field is set to the proper information if someone decides to change it (not sure why they would). 

 

 

I actually tested out this functionality internally, and found that if you remove rights to edit a field, that field will not be populated. That is unfortunate, but understandable.

 

Thanks for the help

0 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.