View Article
28

In DNN 4.3.4, a new mechanism of handling user profile information was introduced, and with it came some new methods of the UserController class.

One method, called GetUsersByProfileProperty, allows a programmer to search on any profile characteristic being tracked by the portal. A typical use for this method in a custom module is to narrow down to a subset of users in the portal, based on the desired profile property's value. But, in this usage, only three of the six or seven parameter items are of any real interest if you want to get all the matches:

  • portalId
  • propertyName
  • propertyValue

Now, it would be nice if there was an overloaded version of this method that just took these three parameters, but there isn't. So what do you put in the other parameters? Here's what I've found:

  • pageIndex - This needs to be set to -1, otherwie you may not get any results at all
  • pageSize - Zero (will be set to zero for you if you set pageIndex to -1)
  • totalRecords - Zero (will be set to zero for you if you set pageIndex to -1)

Well, this is just another tidbit in learning about DNN's inner workings. Bye!

Comments

Philip Beadle
Thursday, October 29, 2009 5:08 PM
Thanx, forgot about the -1 for PageIndex.

Post Comment

Name (required)

Email (required)

Website

CAPTCHA image
Enter the code shown above in the box below