Setting up an NFS share with more than 500 users can be confusing

[gcooper]

UserField?._reroll does some interesting things with 500+ users and groups. Here's some of the code I'm referring to (on 8.0.3):

    def _reroll(self):
        if len(FreeNAS_Users(flags=FLAGS_DBINIT|FLAGS_CACHE_READ_USER|FLAGS_CACHE_WRITE_USER)) > 500:
            if self.initial:
                self.choices = ((self.initial, self.initial),)
            kwargs = {}
            if len(self._exclude) > 0:
                kwargs['exclude'] = ','.join(self._exclude)
            self.widget = FilteredSelectJSON(url=("account_bsduser_json", None, (), kwargs))
        else:
            ulist = []
            if not self.required:
                ulist.append(('-----', 'N/A'))
            ulist.extend(map(lambda x: (x.pw_name, x.pw_name, ),
                             filter(lambda y: y is not None and y.pw_name not in self._exclude,
                                              FreeNAS_Users(flags=FLAGS_DBINIT|FLAGS_CACHE_READ_USER|FLAGS_CACHE_WRITE_USER))))

            self.widget = widgets.FilteringSelect()
            self.choices = ulist

The code when the userlist is <500 is very easy to understand and intuitive (it displays N/A as the first choice unless a user/group is selected). The code when the number of users and groups >= 500 isn't as intuitive (displays a blank line).

Procedure:

1. Join the system to an AD forest or LDAP global catalog with more than 500 users.
2. Try and create a new NFS share.

Expected result:

• I should see N/A as the first option for the user.

Actual result:

• The first option displayed is .

Workaround:

• Just press enter and it will interpret the value input the same as N/A.