Marcelo Sauaf
My feedback
-
14 votes
An error occurred while saving the comment -
4 votes
-
5 votes
-
2,322 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…
-
10 votes
-
14 votes
-
12 votes
-
60 votes
-
182 votes
An error occurred while saving the comment definitely a MUST, it's usual to employ calculated columns to create items' (friendly) PRIMARY KEYs
-
14 votes
An error occurred while saving the comment BUMP
a must to list for n-n entity relationships -
18 votes
An error occurred while saving the comment this is a MUST have
-
23 votes5 comments · Sites and Collaboration » Workflow, Flow, and PowerApps integration · Flag idea as inappropriate… · Admin →
-
135 votes6 comments · Sites and Collaboration » Workflow, Flow, and PowerApps integration · Flag idea as inappropriate… · Admin →
-
219 votes
-
124 votes
-
1 vote
-
236 votes
An error occurred while saving the comment this is another "a MUST", nonetheless still not even a "thinking about"? this user "voice" seems yet another MS political correctness only "initiative"...
-
395 votesthinking about it ·AdminSharePoint UserVoice Admin
(SharePoint UserVoice Admin, Microsoft SharePoint)
responded
Thanks for your suggestions. We agree this can be a little restrictive and we’re going to look into it.
An error occurred while saving the comment yup this is indeed a MUST otherwise we're stuck in relying in external URL shortening providers like bit.ly (that in certain cases, alas, we're not allowed to use due to security matters)
-
375 votes
-
1 vote
well this is DEFINTELY an yet OLD and MUST HAVE for any serious use for SPO since many information nowadays is shared through or even dependable from ctrl-c ctrl-v of images.
making us to "save" an image to add to an enhanced RT field nowadays is just unnaceptable.
SPO / SP2019 should receive the form post and JUST KEEP the html-coded part of the image pasted, since the rendering after in a form or webpart is browser, not server based.