When creating a Form, I need to create forms that has to be sent out to not only staff but also external private emails. Currently there is no way of externals to access the link to the Form unless I select "Anyone with the link can respond" but that then means that all responses will return as "Anonymous" which does not help me tracking who has responded and who has yet to respond. Is there a way that you could allow for the option to either have the responses as "Anonymous" or have the responses show the email address of the person responding?

It is very hard to import from / export to Sharepoint lists into / from MS SQL Server on a computer without admin rights. Both are Microsoft products. I am an BI expert based on Microsoft technologies since 1999 and MS products are the most terrible data sources and targets: Excel and Sharepoint.

It is very hard or not possible to automate ETL between Sharepoint and SQL Server on a system without admin rights and without "Flow" premium features.

• SSIS OLEDB provider doesn't work in SSIS, because the Sharepoint connection string doesn't comply with the standard and SSIS will support only the standard (Microsoft is blocking Microsoft)
• SSIS OData Source components require admin rights to install some Sharepoint SDK. It can't be used without admin rights and without supporting the installing by the IT department, because it "is not listed" and all these things.
• "Microsoft Flow" to copy data from and to SQL Server is a premium feature. Nobody will allow me to buy a premium package only to import some Sharepoint lists into mssql.
• Free "Microsoft Flow" can be used export Sharepoint list to CSV, but to export on a network drive a gateway needs to be installed on a 24/7 computer, and of course admin rights are required, so I can't install and use a gateway.
• Free "Microsoft Flow" from Sharepoint to CSV in OneDrive works fine. But how to copy from One Drive to a network drive? Windows job scheduler would be fine to set up some synchronization each hour, but this requires special rights and the IT department will not grant this rights

https://developercommunity.visualstudio.com/content/problem/1217716/ssis-oledb-sharepoint-connection-error-it-must-con.html?childToView=1224908#comment-1224908

The Microsoft SSIS team writes:

According to public doc of OLEDB connection string, the connection string items need to be key=value format.

These are the docs: https://sqlprotocoldoc.blob.core.windows.net/productionsqlarchives/MS-OLEDBSTR/%5bMS-OLEDBSTR%5d.pdf

The Sharepoint connection string doesn't comply with the standard. The issue is the "WSS;"

Provider=Microsoft.ACE.OLEDB.12.0;WSS;IMEX=1;RetrieveIds=Yes;DATABASE=https://mysharepointsite.com/documents/;LIST={5999B8A0-0C2F-4D4D-9C5A-D7B146E49698};

Microsoft promotes Sharepoint Lists and Microsoft Lists, users are using them. But we, the dwh developers, working with mssql and so on, we get a headache.

Why Microsoft can't provide a free way not requiring admin rights to move data between Sharepoint and MSSQL?

Why you can't make the MS SQL Server integration part of the free Microsoft flow? Isn't it enough when the customer will pay for SQL Server licenses? Why this needs to be a premium feature?

Why the Microsoft Sharepoint team can't follow the Microsoft OLEDB standard and allow using valid connection strings in Microsoft SISS?

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.