network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 4 months |
| seen | yesterday | |
| stats | profile views | 2 |
|
May 7 |
awarded | Supporter |
|
May 7 |
accepted | Unauthorized access to User Profile Service web service |
|
May 3 |
asked | Unauthorized access to User Profile Service web service |
|
May 1 |
accepted | Have FBA users visible (via people picker) to a non-FBA site |
|
Apr 30 |
asked | Have FBA users visible (via people picker) to a non-FBA site |
|
Apr 8 |
awarded | Student |
|
Feb 7 |
asked | using search to display list content for anonymous user on publishing site with lockdown mode |
|
Jan 29 |
comment |
Add 'Display Name' in discussion list Thanks- unfortunately, that's what I'm trying to avoid. I would like the users to be able to choose a name that would be used exclusively for the discussion board. For some it might be their actual name, but for the more privacy-conscious, it could be 'cowboy72' or a more vague handle of their choosing. |
|
Jan 28 |
asked | Add 'Display Name' in discussion list |
|
Jan 28 |
awarded | Scholar |
|
Jan 28 |
accepted | Why not use Sharepoint 2013 as just a backend for REST / CSOM clients? |
|
Jan 24 |
awarded | Tumbleweed |
|
Jan 24 |
comment |
Why not use Sharepoint 2013 as just a backend for REST / CSOM clients? Thanks! Can you give me some examples of things that aren't supported with REST / CSOM? About selecting a different DB- I see your point. I guess it depends on what it's a back-end for. If I'm building a front end to a CMS (not for admins) or a document sharing app- perhaps any situation where you can leverage the SP UI for admin users, but want to demand no SP knowledge to the end-user, then this might be a good case? |
|
Jan 24 |
asked | Why not use Sharepoint 2013 as just a backend for REST / CSOM clients? |
|
Jan 17 |
asked | Claims FBA with a remote active directory membership provider |
