​Hi,

I'm a newby, so be nice to me ;-)

I've inherited a DNN Intranet website.

We use the Member Directory Module, but the search doesn't perform as I would expect.

If I set the filters & Sorting to NO filter, and I search for people from ICT, I only see 2 employees instead of 6.

The database fires this query: Exec dbo.GetUsersBasicSearch  0, 99, 0, N'LastName', 1, N'DisplayName', N'ict'​

The two people it fi

nds have ICT in their displayname.

I altered the Stored Procedure GetUsersBasicSearch ​ so it also looks at functions and departments, but I wonder if that's a good idea, what happens when we get an upgrade, do I need to re-implement my changes to the Stored Procedure?

Joseph, Membership Directory module is part of the DNN Distribution (maybe not the best one, though).

Marianne, GetUsersBasicSearch is able to search for a text in a single column only - in your case "Displayname" (the forth parameter "LastName" is used for sorting).
GetUsersAdvancedSearch supports search for a text in multiple columns and it depends a) on the module configuration, which procedure will be used and b) on the DNN version, whether the stored procedure returns proper records (as this stored procedure has been modified nearly every DNN version since 7.1).
Note that Membership module checks for permission and passes ViewingUserID when calling GetUsersAdvancedSearch - but using a wrong version (See https://dnntracker.atlassian.net/brow...). You'll find a list of all known issues with Membership module at https://dnntracker.atlassian.net/brow....

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN