Audio (mp3) files currently do not preview OR link to the audio file itself (they link to the file details page) unlike video (mp4) files in search results. This causes a poor user experience when searching for audio.36 votes
When searching for a document/folder, if you find it, you cannot Move/Copy it. You have to manually navigate to the exact document library path location to use the “Move/Copy” features.
Please help improve this.29 votes
Change or add new automatically created search managed properties to have the same type as site columns
Automatically created managed properties in SharePoint Online (and on-prem) are created from their corresponding site columns always as text (details at https://docs.microsoft.com/en-us/sharepoint/technical-reference/automatically-created-managed-properties-in-sharepoint). Basically, these managed properties are being created as textual representations of the values of their corresponding site columns. The problem with these approach is that we can only make free search queries with these managed properties even if the corresponding site column is of type Date or Decimal for example. With this approach, more intelligent queries according to the site column data type as range queries cannot be performed. Here are some examples of queries cannot be performed with these automatically created managed properties:
Date based query example #1: SiteColumnNameOWSDATE>1/1/2018
Date based query example #2: SiteColumnNameOWSDATE>1/1/2017 AND SiteColumnNameOWSDATE<1/1/2018
Number based query example #1: SiteColumnNameOWSNMBR>1000
Number based query example #2: SiteColumnNameOWSNMBR>500 AND SiteColumnNameOWSNMBR<1000
If we need to make queries with the same type as the corresponding site columns, the current solution is to use Refinable managed properties (there is a limited number of available Refinable managed properties, depending on its type). There are here very limiting numbers like 10 RefinableDecimal managed properties or 20 RefinableDate managed properties.
I understand that there have to be limitations on the amount of freedom each tenant or farm can have to change the search schema (because of stability/scalability/performance) but I also believe that having automatically created managed properties to be generated with the same data type or an inferred type from their corresponding site columns, would make SharePoint Search a much better solution without the current limitations since automatically created managed properties would be created with the data type developers and users want to query data and would allow both users to find the information they want and developers to build better search based solutions, making more intelligent search queries and taking full advantage of the queries that each data type supports (imagine a database with a column of type number where we cannot make a range query like column > 0 or column < 100 for instance, it just doesn't make sense).
Here are some advantages if automatically generated managed properties are created with the same data type or an inferred type from their corresponding site columns and not always as text:
• Users and developers would be able to make all types of search queries the data type of the managed property supports
• Assuming users want to search the information they create and developers want to build solution to search data users create, virtually there would be almost no need to map automatically created crawled properties with existing Refinable managed properties because automatically created managed properties would have the type users want to query
• This change would not bring more load on search and would prevent developers to need to create new managed properties or manually map their crawled properties with Refinable managed properties because the managed properties they need are automatically created by SharePoint
• The number of Refinable managed properties could be reduced since developers resort to these managed properties because automatically created managed properties don't have the data type they need
If changing the existing managed properties can lead to compability issues, instead of changing the existing managed properties, I ask you to add additional automatically generated managed properties that are created with the same data type or an inferred type from their corresponding site columns.
Automatically created managed properties in SharePoint Online (and on-prem) are created from their corresponding site columns always as text (details at https://docs.microsoft.com/en-us/sharepoint/technical-reference/automatically-created-managed-properties-in-sharepoint). Basically, these managed properties are being created as textual representations of the values of their corresponding site columns. The problem with these approach is that we can only make free search queries with these managed properties even if the corresponding site column is of type Date or Decimal for example. With this approach, more intelligent queries according to the site column data type as range queries cannot be performed. Here are some examples of queries cannot be…87 votes
If you deploy a SPFx application extension to a site for a header/footer, this shows on most pages, but not on the search page.
Would be nice if custom headers/footers showed on the site search page as well.60 votes
Improve the accuracy of search in Chinese or allow administrator to adjust / customize word-breaking in Chinese search scenario in SOP
In SharePoint O365, the search engine 's Performance is not always satisfactory,especially in Chinese. Sometimes, the search result does not match the search criteria. This issue was analyzed by MS SPO Support team and the root cause should be the incompleted word-breaking.
User expected a better search engine in Chinese Search so that the expected result could be find out directly.
As an alternative, user also expected that the customising feature for word-breaking dictionary could be offerred in SPO.26 votes
This idea is to enable SharePoint search to perform optical character recognition of images (incl. scanned PDF documents) when they are crawled by the SharePoint hybrid crawler. This will make it possible to search for text inside images (and scanned PDF documents) and find these documents more easily. Today, it is not possible to search for text inside such images or documents.32 votes
Pages created using a page layout (layouts created via the Design Manager, no additional custom code, only what was provisioned by the tool), don't get indexed and therefore aren't searchable.
Pages that can't be searched become pretty useless as users aren't able to find them and they can't be displayed in any search-based web parts.
This issue has been known for over two years now - please fix it asap.34 votes
In WSS 3.0 (SharePoint 2007), when we searched a blog, it gave us the option to sort results by Relevance (the default) or by Modified Date. Now in SharePoint Online, when you search a blog, it gives you no sort options, but seems to list the search results in random order. This is a step backwards in my opinion. We need to be able to sort by Modified Date again.6 votes
Please provide a way to gather analytics for the Modern Search. We are using Communication templates for our Intranet and need know what users are searching for.
An equivalent to what is available from the SharePoint Admin Center > Search > View Usage Reports.3 votes
Current modern search in communication/modern team site defaults to local scope and search results are from the current site. Users has to click on the SharePoint link from breadcrumb in order to expand the search scope across sites.
Most of our customers prefer to search on the broader scope rather than searching on the current site, esply. for the Communication sites.49 votestell us more · AdminSharePoint UserVoice Admin (SharePoint UserVoice Admin, Microsoft SharePoint) responded
Thanks for your feedback! We’d like to understand better. It would be useful to know in which cases you think that your customers actually would want to search on the current site?
Improve the behavior that reloading the search result when opening a file after searching SharePoint Online library
I request not to reload the search result page when searching and sorting Office files, such as Word documents in the SharePoint Online library. Because if I click a file to open on Internet Explorer 11 in document mode 10 by using Windows 7 PCs, search page would be reloaded and results are disappeared.
For Windows 10 PCs, the page wouldn’t be reloaded if I selected Name (linked to document with edit menu) as Column name in Settings, Edit View. I would request the same behavior for using Windows 7 PC.3 votes
We have several business needs which rely on easily searching and consuming information across our sites. While we appreciate the work so far that's gone into modern hub and site structures, we would like to be able to customize the default hub site search part. Particularly, we want to be able to add additional Refiners. We already have the required refiners in our site's defined search schema, why not allow us to add additional refiners to the search experience?23 votesthinking about it · AdminSharePoint UserVoice Admin (SharePoint UserVoice Admin, Microsoft SharePoint) responded
Thanks for your feedback! We’re reviewing your suggestion. Remember, the more votes a suggestion gets, the more likely it is that we’ll do it.
Option to open document either by web browser or local application when searching.14 votesthinking about it · AdminSharePoint UserVoice Admin (SharePoint UserVoice Admin, Microsoft SharePoint) responded
Thank you, then we understand. We’re taking your idea into consideration.
Using the search at the top left of the site contents page has a filtering impact on the contents and subsites listings. This functionality is a complete divergence from the search experience in other parts of SharePoint. There should be a way to send all search boxes to the same search results page, instead of this rather confusing setup.4 votes
For manual download the OOTB SharePoint reports from SP admin page- SharePoint Online admin portal> Search> Search Reports.
Multiple reports available OOTB, but no API/Powershell available for Search Analytics, by which we can export custom Search reports or we can schedule the download of OOTB reports Monthly.
Provide API/Powershell for managing/automating SharePoint Search reports.5 votes
To the Microsoft Team: Thanks for keeping up the good work while listening thru the "user voice"!
If you have to believe this, there have been at least 10 of my customers who have requested an "EXPORT to CSV" feature on the People Results page. I have seen a lot of other products having the export functionality, and would love to see this added in the SharePoint Online platform.2 votes
The setting "Always index all Web Parts on this site", is not yet exposed trough CSOM.
This setting can be found in site settings > Search and Offline Availability > Indexing ASPX Page Content
This is usefull when using sites with broken permissions, which are then not indexed as needed.
Please add this functionality to CSOM.
It is this property: web.ASPXPageIndexMode = WebASPXPageIndexMode.Always;3 votes
When viewing search results from a Document Library Search, the Quick Edit option is not an available feature. It would be great if this option was available.1 vote
- Don't see your idea?