Please follow the steps below :-
Open SharePoint Central Admin.
Navigate to Search Service Application.
Open “Search Schema” from the left navigation.
Search managed property “ListItemID”.
Make sure that the “Searchable” checkbox is selected.
Click "OK" to save changes.
Run the full crawl.
Below are the possible situations happened in the back-end,
Particular user's Birthday was modified in the user profile.
Mapping of the Search Crawl proeprty "RefinableDate00" with User Profile managed property "SPS-Birthday" is modfied.
User's profile sync happened with Active Directory, and Active Directory may be update the empty value!
Please checkout ...
My guess is that either somebody has modified the search resultat source you are using or the mapping has changed or you are using another context. What does the SP Search Query tool shows for that query?
We use SharePoint 2013 and we had it a few times that this did not work either. In our case resetting the index and performing a fresh full crawl solved our issue.
In case you try this and resetting the index throws an error you might want to take a look at this: Index reset throwing exception
I experience this very often, sometimes it takes anywhere from 1-24 hours for the managed properties to index and get crawled. Since in SharePoint Online you do not have a way to kick off the timer job. You may just need to wait up to 24 hours. It does appear that you have everything configured correctly though!
Crappy, but unfortunately this is how it is ...
You can always manually edit the topology with powershell. As far as the topology goes, it really depends on what you are trying to achieve. If you want HA then both search servers will need to have all the search rolls running on them. If you are looking for speed then you would divide up the the rolls between the two servers.
You either need to crawl the content in place or replicate the content to a server closer to your Crawler. Solutions like DFS and others can help. You could also stand up a new crawler, but DFS is a much easier solution. You can use Server Name Mapping to ensure that the File Server route is reflected correctly in the Search Results.
Goto Central Administration
Manage Web Applications
Select the web application
Click on Service Connections
Ensure that the search application you configured is checked in this list.
Thanks to Development 4.0
You need to add additional property in the query EnableDynamicGroups:true.
By doing this, you will be able to fetch data from Team site. By default, results from private O365 groups is not included.
So, modify your query as below:
Reference - Retrieving search results ...
Check if your serve has the Search Service Proxy or not.
If it exists then delete and create new.
If does not exist then create the new using below command.
$searchServiceApp = Get-SPEnterpriseSearchServiceApplication
New-SPEnterpriseSearchServiceApplicationProxy -SearchApplication $searchServiceApp
Refer to below links for more details.
You can use the filter to select needed items. For the columns you want to search, click on the down arrow and select filter to choose the name you are willing to search. It can be done on all your columns.
So far, we can't do this, both online and on-prem versions can't do it.
As a workaround, you can export version history, which makes it easy for you to view.
You can refer to this similar situation below:
Exporting item list version history