PaulE
My feedback
-
29 votes
An error occurred while saving the comment PaulE
supported this idea
·
-
47 votesPaulE
shared this idea
·
-
8 votes0 comments · SharePoint Dev Platform » SharePoint APIs (CSOM/REST/Server-side) · Flag idea as inappropriate… · Admin →PaulE
shared this idea
·
-
139 votes5 comments · SharePoint Dev Platform » SharePoint APIs (CSOM/REST/Server-side) · Flag idea as inappropriate… · Admin →
Thanks for your feedback! We’re reviewing your suggestion.
An error occurred while saving the comment PaulE
commented
Would certainly simplify an app using a REST query for list items. Instead of returning everything and then using your own code to trim down the results to just those which match the Audience, the REST response could be significantly smaller if the REST API did this for you.
Being the Audiences is not security, it's not a "problem" that the REST API does not do the filtering aside from the workaround suggested in the previous paragraph.
Would be nice to have.
-
1 vote1 comment · SharePoint Dev Platform » SharePoint APIs (CSOM/REST/Server-side) · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment PaulE
commented
Default limit on a REST query is 100 items. You can change the default up to "$top=5000". When there are more results for the query than returned, a link is given in the REST response to get the next "page" of results.
As in all queries to a list, if the list has more items than the threshold allows, you need to use filters against columns which have been indexed in order for the query to match fewer than the item threshold. Then, the query results can be constructed and returned in "pages" as described in the previous paragraph.
-
61 votesPaulE
supported this idea
·
An error occurred while saving the comment PaulE
commented
At Ignite 2017, I thought I saw an example of grouped commands (grouping in the item context menu, sub-menu in the list commands bar), but I haven't been able to find any information on it and would have to spend hours going combing through the videos of the sessions I attended. It would appear from the code found in listview-host-assembly-[locale]_[hash].js that this would not be supported. Sure would be nice if it was!
-
51 votes
Thanks for your feedback! We like your suggestion and it’s being added to our backlog. We don’t have yet specific schedule for this, but item has been added to upcoming plans for the SPFx and since request does make sense and has been requested from other sources as well, this will be most likely implemented.
PaulE
supported this idea
·
An error occurred while saving the comment PaulE
commented
An event handler for cleanup when the web part is removed would be very handy.
-
40 votesPaulE
supported this idea
·
An error occurred while saving the comment PaulE
commented
Yes, limiting the emails to addresses found in UPS is really crimping our style!
-
746 votesPaulE
supported this idea
·
An error occurred while saving the comment PaulE
commented
"InPrivate Browsing" and "InCognito" don't get you very far when the browser is configured so you automatically log in within a trusted domain. Opening the browser as a different user is some times not possible because a user profile will get created that can cause issues with that account being used autonomously. Manually creating the URL using the pattern found in SP2010 for "Sign in as a different user" is usually my workaround.
Truly! What a pain to create a set of links on one modern page and then have to re-create it in order to have it on another page. Really need a data-driven Quick Links web part where we can add/remove/edit a link in the dataset and each page with the Quick Links using that dataset is automatically updated.