Hi _ Kris Dai,
Thank you for your response!
I have seen @JonFrost's thread before and have seen the pre-load method described in the blog you referenced. The one issue with pre-loading the way the blog states is, as far as I can tell, there is no unique numeric id field available to bring in using office365Users.SearchUser() function. the Id field that it does bring in is a mix of numeric and character string.
The method that I am currently employing is to:
1) grab the first 999 records and store them into a collection, using: (ClearCollect(coll1, SortByColumns(Office365Users_2.SearchUser({searchTerm:"", top:999}), "Id", Ascending)))
2) grab the last set of 999 records and store them into a collection, using: ClearCollect(coll2, SortByColumns(Office365Users_2.SearchUser({searchTerm:"", top:999}), "Id", Descending))
3) combine the 2 collections together into one single collection (I realize this may double up records but I then group the collection to get rid of any duplicates and get unique values)
The thing I am unsure of is if my method of Reversing the sort order actually pulls in the last 999 records or if it pulls in the first 999 records and then reverses that order. I can't test this because we do not have over 999 users yet. As far as I am aware, the SortByColumns is a delegable function but I am unsure if the Office365Users connection is delegable or not.
Would you have any insight if using SortByColumns on Office365Users is actually doing what I think it's doing?
Thanks for your input!
-Aaron