Hot answers tagged managed-property
4
Try using a KeywordQuery and setting the RankingModeID to "D9BFB1A1-9036-4627-83B2-BBD9983AC8A1"
This PowerShell code works for me
Add-PSSnapin Microsoft.SharePoint.PowerShell
$site = get-spsite "http://localhost"
$kq = new-object Microsoft.Office.Server.Search.Query.KeywordQuery($site)
$kq.ResultTypes= ...
4
A similar question has been asked before:
http://stackoverflow.com/questions/166178/searching-date-meta-tags-in-sharepoint
The short answer involves writing your own protocol handler - not for the faint hearted, but it should work nicely.
3
You didn't mention it in your question so just to make sure...
Did you perform a Full Crawl of the content source AFTER you mapped the ows_DueDate crawled property to the TaskDueDate managed property?
Do you know for sure there is content with a value for the ows_DueDate crawled property?
SOLUTION:
The problem was due to teh fact that the ...
2
Html content is usually in the crawled property:
Property Set: 11280615-f653-448f-8ed8-2915008789f2
Variant type: 31
Name: html
(http://msdn.microsoft.com/en-us/library/ff795815.aspx)
You can also add a "Spy" stage to examine what crawled properties are available in the pipeline - and see if you can find the one with the correct content. Or enable ...
2
Not sure, it makes any difference but a detailed thread from someone who faced similar issue. The person seemed to have contacted MS Support as well, so you'll see a lot many updates. Here's the article.
2
you can create a calculated column(test) with last updated column, do full crawl and find the crawl property ows_test and map that to your new managed property. and specify the new managed property(text) as column in your sortablecoreresultswebpart. you will get something like this
1
12/5/2012
datetime;#2012-12-05T16:26:10Z
you can use ...
2
You can use PowerShell to create a Crawled property and a managed property.
You can use the following code to create and map the properties
Param(
[string]$crawledProp,
[string]$managedProp,
[int] $typeManagedProp
)
# TypemanagedProp 1 = Text 2 = Integer 3 = Decimal 4 = DateTime 5 = YesNo 6 = Binary 7 = Double
$snapin = ...
2
It's there now. I think it was the combination of needing documents in place and a full system crawl, before the crawled properties appeared in the properties store.
For others: such properties in SharePoint will appear with the prefix ows_. In fact, there can be a couple thousdand of these, most taken from the default SharePoint infrastructure. Several ...
2
This is how we configure crawled props (before indexing them!):
New-SPEnterpriseSearchMetadataCrawledProperty -SearchApplication $searchapp
-Name publishdate -Category Web
-IsNameEnum $false -VariantType 64
-PropSet "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXX" -IsMappedToContents $true
Variant type is 64 - which is the date/time type. Add the ...
2
You have to use a pipeline extensibility stage which reads the text based property and writes it back to a new crawled property of type int, which you can map to an int based managed property.
I've done the same for date <meta> tags in web pages which are interpreted as text, but you want them as dates.
I have a powershell prototype sample here which ...
1
I think you can make a call like this to get the values for owstaxidmetadataalltagsinfo refiner:
http:// siteurl /_api/search/query?querytext='*'&refiners='owstaxidmetadataalltagsinfo'
You will get some values with this format:
L0|#036f7c08a-0176-47e9-9d70-070291ce0e32|Data Warehousing
1
You can review the list of search operators in this article but there isn't one that will let you pass multiple values for one property. You can however remove the OR to save some space.
When you use multiple instances of the same property restriction,
matches are based on the union of the property restrictions in the KQL
query. Matches would include ...
1
You can use SPSecurity.RunWithElevatedPrivileges. this is a delegate method that is to run with elevated rights. This method runs under the Application Pool identity, which has site collection administrator privileges on all site collections hosted by that application pool.
For example:
SPSecurity.RunWithElevatedPrivileges(delegate()
{
...
1
At the bottom of Manage the search schema in SharePoint Server 2013, it describes the use of these "unused managed properties". It states:
The following table provides an overview of the default unused managed properties that you can reuse and rename using an Alias.
and continues with a table of managed properties that are shipped OOTB, but that are ...
1
in my opinion, the crawled properties in both section should be the same.
You are not correct. FAST Query administration page has two section with access to managed properties and even link to Content Sources (under Crawling).
The reason for this is the fact that People Search does not go through FS4SP but instead uses the built-in SharePoint Search. ...
1
You set the scope against the "contentclass" not a property itself. You then restrict the search down to that content type, and then you query on that single field in your search method be it a search webpart or a code behind query.
To see how this works look at the "People Scope" which implements this already.
So your query then would become:
...
1
Did you add the column in the core results webpart properties? There is a property where it's an xml document which says which columns to return in the search results. Without your column being in that xml, that column won't appear in the data sent to the XSLT, and thus, you just getting an empty value in the XSLT transformation.
1
I think that is not possible - you would have to implement a custom ranking layer between search and the search result webpart for the sorting.
I would not recommend this for an enterprise - for a custom, specialized searchsite with limited queries it would be an option.
Hope it helps!
Max
1
Have you added the properties you want to retrieve in the Managed Properties section of the Service Application? Note that this is different from the 'Managed Metadata' Service Application (perhaps poor naming on MS' part). You'll also want to ensure that the Managed Properties you have are included in the index.
1
I think that will be hard. My best guess:
Create a separate search center/search page per language, and map your refiners on the locaized values. You should use a valuemapping + customfilter for this one: http://msdn.microsoft.com/en-us/library/ee819920.aspx
Using this technique, you can map the value 1 on, for example, red, rojo or rood. It requires you to ...
1
I believe that the data that you get from crawled property is IEnumerable. So, I wonder that how you convert it into byte[] and then string?
I have tried this with no success because the "invalid character in a Base-64" is retuned.
XDocument inputDoc = XDocument.Load(args[0]);
var data = from cp in inputDoc.Descendants("CrawledProperty")
...
1
You have to make sure the column which holds the duplicate value is of type integer. Columns or site columns created via SharePoint UI is of type Decimal. You can perfectly well map a decimal type crawled property to an integer type managed property, but it just won't work. And there is no error given.
So either create an integer site column which you add ...
1
Did you check "Include values for this property in the search index" for both of the ContentTypeID crawled properties?
From http://technet.microsoft.com/en-us/library/cc164182.aspx
"On the Edit Crawled Property page, if you want to include values for the crawled property in the search index, select the Include values for this property in the search index ...
1
It seems the field is of data type Text (with content which represents a date), since it's crawled as Text. If you want to use the field for dates with time, you have to set the data type of the field (the data type of the column in the list or library) to Date and Time. Then it will be crawled as a real Date and Time data type and the mapping will be ...
1
If you click on the Crawled Property link (crawled properties usually begins ows_ as opposed to the Managed properties, which are linked to the crawled property) the page should have a link to some items with that property in use (and set).
You may need to ensure the property is included in the index before it'll show up in that page.
For me, this works in ...
Only top voted, non community-wiki answers of a minimum length are eligible
