Is someone at Microsoft can give a feedback for this feature request? Not responding to uservoice does not look really professional.
Not having this feature make the web part almost useless in real case business usage.
Hope Microsoft is looking at userVoice... This feature should have been available from the begining.
3 votestell us more · AdminSharePoint UserVoice Admin (SharePoint UserVoice Admin, Microsoft SharePoint) responded
Thanks for your feedback! Are you seeing this in SharePoint Online or an on-premises SharePoint Server version?
To Microsoft: The issue is with the maptocion api (_api/web/maptoicon) that returns incorrect image url.
For zip file it returns _layouts/15/images/lg_iczip.gif. The image does not exists. Instead it should return _layouts/15/images/lg_iczip.png
For msg file it returns _layouts/15/images/lg_icmsg.png that does not exists. Instead it should return _layouts/15/images/lg_icmsg.gif (However, the issue here is that you should provide the png file...)
1,136 votesworking on it · AdminSharePoint UserVoice Admin (SharePoint UserVoice Admin, Microsoft SharePoint) responded
As per the Message Center Post MC187289 we have started to roll out Site Swap. This is a new PowerShell cmdlet Invoke-SPOSiteSwap that will enable you to swap your existing root site with a Communication Site. For further information please refer to https://aka.ms/SiteSwap.
Can someone @microsoft confirm this approach to be valid? Looks to me the right way to do it for business who can't wait forever : https://www.spjeff.com/2018/12/31/video-create-modern-communication-for-root-site-in-tenant/
Please provide a REAL durable link functionality that support files being moved anywhere in SharePoint. And also provide a real MOVE functionality that is not implemented using a copy & delete.
This lack of crucial features and low vote rate let me think that SharePoint is not really being used as a real, solid EDMS system. Wake Up Microsoft or at least let us know where you are going with this.
We are happy to share that we are actively working on it. We will be sharing more details about the plans at the SharePoint conference in Vegas.
Here is the MS road map item
Here’s the session we’ll share more details.
Is someone at Microsoft can give an answer on this one? This requirement has been posted more than a year ago…. The feature is a must for international organizations wanting to use modern experience.
1,439 votesworking on it · AdminSharePoint UserVoice Admin (SharePoint UserVoice Admin, Microsoft SharePoint) responded
As of March 2019, this feature should be available to 50% of users in Targeted Release. The rollout to all users is continuing, but there are several features included together in this one and we’ve paused the rollout a few times to accomodate changes based on feedback to the other features. New ETA for reaching all users is April 2019.
Note this feature will only apply to modern doclib and list UX in SharePoint Online
89 votes4 comments · Sites and Collaboration » Workflow, Flow, and PowerApps integration · Flag idea as inappropriate… · Admin →
Hard to understand why it was not provided same time as list forms support. Only 7 votes ???
We should also have the possibility to disable the information panel metadata editing. When using PowerApps with list to do metadata entries, the information panel gives to possibility to bypass PowerApps that could integrate validation logic. I think this could be implement using the "Launch forms in a dialog" list/library advanced options, where "Yes" would force to use the form and disable the metadata update using the information panel. Customizing forms with PowerApps is also supposed to be available for library...
Metadata entry in modern page is a non sense. When you open the information panel for a document/list item and edit the properties, each property that you update increment your version number (so when you add a new document, if you have 4 properties to fill out, the version number will start at 5. Completly ridiculous!). If you use the "edit all" option, you need to be very carefull when filling out the properties because if you click outside the properties pane, the panel will close and you will loose your properties updates. This is very frustrating for end user if one of your property is a description and loose the info because you click outside the panel. This add up to other user comments in this thread and there are other issues with modern experience for metadata entry but I will stop here. So my question is: What is all this mess with the modern experience? How come there are not more complaints (are the 100 billons users licenced are really using modern experience with SharePoint libraries? I guess not… so probably why Microsoft is doing nothing about this…). This is unacceptable. Period.
1,661 votes37 comments · SharePoint Dev Platform » SharePoint APIs (CSOM/REST/Server-side) · Flag idea as inappropriate… · Admin →
We do apologize a delay here, but are actively working on this and we should have an updated status available on summer or autumn 2019 for starting preview of this capability with our customers and partners.
More than a year for this BIG hole in the SharePoint REST API. This would be understandable if people where not really using term store but I don't think that is the case....
We initially didn’t enable the full width column on team sites due to the vertical navigation on the left and left justification of team site pages. How do you imagine it should work/look on those pages?
1 vote0 comments · SharePoint Dev Platform » SharePoint APIs (CSOM/REST/Server-side) · Flag idea as inappropriate… · Admin →
1,126 votesworking on it · AdminSharePoint UserVoice Admin (SharePoint UserVoice Admin, Microsoft SharePoint) responded
We are hard at work on this capability now. We’ll release it early next year.
Really hard to understand that this is not a priority.
90 votesthinking about it · AdminSharePoint UserVoice Admin (SharePoint UserVoice Admin, Microsoft SharePoint) responded
Thank you for your suggestion! We are reviewing this feature request and considering engineering designs and possible timelines.
Just wondering why voting is closed... I really don't understand why it is not a top priority. This is so obvious that it is a requirement for SharePoint to use customers, products data for metadata. If they don't provide an OOB Common Data Service column type they should at least provide the ability to connect with BCS (Business Connectivity Service). I'm probably missing something here. I would give all my vote for this...
Anyone from Microsoft who could provide feedback on this?