Rick Whitelaw Posted October 4, 2014 Posted October 4, 2014 It's my understanding that the List function (across a relationship) should return a list of unique values. In other words, no duplicates. Apparently this is not the case. Instead I'm using Brian Dunning's UniqueValues CF to achieve this end. What's up with that?
bruceR Posted October 4, 2014 Posted October 4, 2014 List returns the list. It has nothing to do with unique values..
bruceR Posted October 4, 2014 Posted October 4, 2014 But if you want to define a value list that shows only related values, define a value list that shows only related values. You don't need a custom function. Example of a value list that includes only related field values
comment Posted October 4, 2014 Posted October 4, 2014 But if you want to define a value list that shows only related values, define a value list that shows only related values. I don't see the purpose of defining a value list anywhere in the question. Granted, using a value list in order to get a list of unique values (through the ValueListItems() function) is bound to be more efficient than any custom function. However, this can only work if the field in question is indexable.
Rick Whitelaw Posted October 4, 2014 Author Posted October 4, 2014 Thanks guys. Not sure why I thought List returned unique values. I've certainly used the function often enough . . .
Recommended Posts
This topic is 3970 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now