5

Is user profiles an appropriate place to store things like number of items per page in a custom grid user selected? (I you can store it in the view, but it won't be per user this way).

My first though was to store these settings in user profiles, but there are problems with access permissions for programmatically creating user profile properties boiling down to you either have to give every user 'Manager User Profiles' permission in SSP or you have to run the application pool under a domain user, not NETWORK SERVICE. Both scenarios are unrealistic for me, so I'm now looking for another way to store such 'per user' settings.

Thanks!

Edit: I'm now considering ASP.NET profile mechanism with an additional DB to store user properties.

Community
  • 1
  • 1
axk
  • 5,316
  • 12
  • 58
  • 96

3 Answers3

1

Given that the information is not sensitive a simple database with values stored against AD login should suffice.

And as you have the ASP.Net user database already, storing the information there would be the best option.

Nat
  • 14,175
  • 5
  • 41
  • 64
0

Maybe a Global List, that is only accessible for the SHAREPOINT\SYSTEM User and that you can then Query in a SPSecurity.RunWithElevatedPrivileges Function.

Disadvantage: You require Custom code to read/write to that list.

Michael Stum
  • 177,530
  • 117
  • 400
  • 535
  • It is an alternative I've also thought about, but I think it would be easier to implement it with the ASP.NET profiling mechanism: no additional fields, content types lists and features. Besides we already have an ASP.NET user database created with aspnet_regsql.exe. – axk Oct 31 '08 at 14:38
0

Cookie?

Sure they have limitations, but it is fairly easy to create the control to run javascript to add/edit the value

Nat
  • 14,175
  • 5
  • 41
  • 64
  • We decided that we don't want this info to be lost when a user switches machines, so this is not an option. Though this would be the easiest way, I think. – axk Nov 02 '08 at 20:04