Mark
My feedback
-
5 votes
-
6 votesMark
commented
Bill, RBS is a joke. It's over complicated and a nightmare to maintain on large farms. Adding 3rd party products increases the total cost of ownership. When evaluating the platform vs others, it's a big hit to SharePoint.
-
20 votesMark
commented
You need to think outside of your environment. For example, if using a hyperlink what would your users do if the URL is an internal URL and they are external to your farm. eg on their phone?
The simple answer is an email reply to. So when you reply "approved" to the approval email it goes to a document library and the email can be actioned automatically via a default workflow on said library.
Note: workflow on the document library needs to be created by a SP dev.
-
571 votesMark
commented
Not necessary.
From windows 7 or 8.
1. Right click on your browser icon in your tray
2. Hold shift down and right click on the browser from within the popup
3. Run as other user
4. Type username and password -
42 votesMark
commented
such a 101 CMS request. The fact this is not included by default (SSL); is ridiculous.
-
1,332 votesworking on it ·
AdminSharePoint UserVoice Admin
(SharePoint UserVoice Admin, Microsoft SharePoint)
responded
We are continuing to make our large list experiences better, please keep the feedback coming.
Spring 2018 update:
- We now support being able to manually add indexes to lists of any size (increased from lists up to 20,000 items previously).
- Starting with the February release of the Office 365 Excel client, you will be able to export your full list instead of getting cut off part of the way through.What we are working on now:
- Predictive indexing will start to work for lists larger than 20,000 items so your views will automatically cause the right indexes to be added to your lists.In our backlog:
- Being able to index/sort/filter by lookup column types (like person, lookup or managed metadata columns) without being throttled.
- Making sure that our REST APIs support querying in ways that will guarantee that the call will not be throttled.For…
Mark
commented
Simple answer is do not use lists and move to a database for all your data requirements. SharePoint lists are nothing short of a joke.
-
57 votesMark
commented
Why would it be fragmented unless they intentionally do so? Its the same product, just on Microsoft's DC. Fragmentation or stopping sale of product will just mean people will shift to Google docs. Hell I know I would rather shift to a free product.
I would prefer it be a simple service app which runs on an app server just like all other dam SharePoint services. Simple consistency would be better.
-
5 votesMark
commented
Either:
1. Improve list performance; or
2. Remove the Share button all together.Mark
supported this idea
·
Mark
commented
Yes this is a massive problem and I agree entirely. The approach to Lists/Libraries needs a good hard rethink, its by no means efficient.
-
42 votesMark
commented
This is more alpha release of the service than an "upgrade". Without question the distributed cache was poorly implemented.
Mark
supported this idea
·
-
11 votesMark
shared this idea
·
-
73 votesMark
commented
Is'nt that just managed metadata navigation??
-
15 votesMark
supported this idea
·
-
5 votesMark
supported this idea
·
-
2 votesMark
shared this idea
·
1. create custom property in UPS
2. Import userAccountControl value
3. Value "0x02" is disabled account.