Expanding on the WebPartFormFactor concept, it would be great to be able to natively get information about the size of the current web part zone hosting the web part. This would allow us to more easily offer optimised UX based on how the web part is being displayed (eg: if the web part is in a 1/3 or 1/2 width zone, show fewer items per row than if it's full-width).

This can currently be achieved with native JS measuring element widths and resize handlers, but it'd be much cleaner and more reliable to have native integration, especially as more layout options are added.

We need an automated Flow for Collect Feedback to replace the Collect Feedback SharePoint 2010/2013 Workflow. I need to route Office documents--specifically, Microsoft Word, or Visio Drawings, Powerpoints, or spreadsheets, to stakeholders (Engineers) for their feedback. Specifically, these are procedure documents that require redlines (Tracked Changes) and the ability for the reviewer to edit/add comments. Word already does that, yes, but I need to be able to run a SharePoint Workflow that is NOT an Approval workflow. It's to be used for collecting redline feedback, reviews, tracked changes, and routing to several users. Not including that Collect Feedback Workflow in PowerAutomate is absolutely killing my division's procedure projects. In a bad way.

Hi All,

I have a customer who is about to walk away from SharePoint online as we can’t get the metadata of the version of the document into the footer. They’re going to go to livelink or docuware.

What’s the problem?

This may sound small but industry standard document management requires that footers of documents can contain metadata, most importantly the version of the document so when a user prints the document the document can have the correct controls embedded right the way through the document. It’s called Document Control.

SharePoint online allows us to create content types and, through a feature called Enable Labels, allows us to create a label and add an metadata to it. We can then add a template to the content type such as a Microsoft Word document and using the quick parts feature in Word add in the label that contains the meta data into the footer.

This worked perfectly in On Premiss SharePoint.

SharePoint online allows us to add metadata it just won’t recognise the version.

I have spent over a week working with Microsoft office 365 support analyst who needed me to give him a demonstration of what I was trying to achieve four days after contacting him he finally understands the problem and sends it onto the ‘specialised team’ I am then told Microsoft can’t do it themselves.

For a product that seeks to dominate document management and control this is absolutely a massive oversight.

I feel after dealing with Microsoft it’s kind of ‘it can’t be done and goodbye’.

I actually think the loss of this function is a massive deal and unfortunately a deal breaker for some

Thanks all

Tony

Dear Microsoft Team,

The author name located on top left corner of UI SharePoint page is linked with "authorbyline" property field.

However after updating this field via PowerShell script and in .NET code CSOM PnP, the change of author name does not sync to the SharePoint page.

It would be nice pragramatically updating the author name is supported in the next release.

This request would bring value to the business when migrating bulk pages from a third party intranet site to SharePoint Online so that instead of manually updating each SharePoint migrated page with the author name and publish it, instead a custom built migration script that I've developed could auto update author name on bulk migrated pages.

Thanks.

Hi.
I'm trying to find a way to create site policies using Powershell together with the PnP framework.
I need to provision new site policies to a selection of site collections on my tenant.
At the moment it's possible to get and set the policies using PnP. But there is no option to add/create a site policy.

ps,
Tried to do the same thing using a PnP Provisioning template. But ran into a, I believe, known error:
Sorry, something went wrong
An unexpected error has occurred.
TECHNICAL DETAILS

Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: ff4b819f-706e-b000-b146-974b303ea185

Date and Time: 10/7/2020 3:19:58 AM

When we have more than 5000 items in a SharePoint Online list which we need to display in a custom form, we can only display 5000 items in the form, and to display more than 5000 items we need to write a recursive ajax function using REST API.
So that it will concatenate the items in each recursion and then can be able to display more than 5000+ items, but each iteration/recursion pulls only 99 items out of 5000+ items at a time.

I have to recursively/iterate the piece of code 50 times to pull 5000 [i.e. 5000/99] items to display it in a custom form, and if the number of items is more than 5000 for e.g.: 100000 then the iteration of code would be 1010.10 times and so on i.e. Number of items/99

Consider a scenario where we have more than 1 lakh items out of which item in between 60,000 to 70,000 have inactive records which are not in use, which need to pull out, so you can imagine the pain in recursively pulling out 99 items in each iteration of code to reach to items between 60,000 to 70,000 or 100000+ items the scenario will be worst if we don’t know where is the inactive items resided in more than 100000+ records.

In a Scenario where there are complex transaction of more than a 100000+ of records to update and display then again it is a nightmare.

As per Microsoft the limitation is to improve the performance of the database and SharePoint

Currently it's not possible to find published to Marketplace SPFx solution on SP2019.

It would be good to have possibility to achieve SP2019 users with SPFx solutions that currently published to Marketplace. Such solutions could have description or even links to packages that could be used for SP2019.

Or if it possible - publish process to Marketplace could be extended with additional package that could be used for SP2019

Another idea is to extend SPFx schema additional property - Url to SP2019 package (or to custom page where additional description could be posted for SP2019 users that want to install SPFx from Marketplace)