New answers tagged

0

It is possible that your Search Service needs to re-crawl the library before the CSWP will index the new results. You may want to also check to see if "txt" is an accepted filetype for Search. By default, it is. https://technet.microsoft.com/en-GB/library/jj219660.aspx?f=255&MSPPError=-2147217396 ...


0

A project I was on had a similar implementation and it worked but with a few hiccups. To answer each of your questions first: Can Continuous Crawling allow you to publish an article immediately? Technically immediately, no, but it will significantly reduce latency. Ours was about 10-20 minutes. FQL does support granularity down to fractions of a second. ...


0

I haven't worked with custom ranking since FAST ESP so apologies in advance if I'm not much help. Sounds like you narrowed it down to name/value/rank for FileType. Here are a few thoughts: Have you confirmed your FileType values match what's in your instance? Is value OK to begin with 0? (An example in the book referenced below starts with 1.) Are your ...


0

If you are using SharePoint 2013 or 2016 this is not difficult. Lets assume that your date field is "RecordDate" and the text field is "RecordText". If you create a managed property of the same name for each you should be able to use the query RecordDate>={Today} OR RecordText="ABC"


0

Try /_api/search/query?querytext='(path=https://portal.xxx.com:443/forum/101/100 OR path=https://portal.xxx.com:443/forum/100100) AND contentclass=STS_Web'&trimduplicates=true&enablequeryrules=false&clienttype='ContentSearchRegular'


0

It can as long as you figure out the authentication. We did it for MediaWiki by creating a Query Time Security Trimmer. It worked well, but does slow the delivery of results. The final solution was to turn on AD authentication. For the ticket system it should not be problem.


1

As stated in the question, the right managed property is body. However such property cannot be used as-is, but it needs to be set as queryable in Central Admin. Of course, an index reset and a full crawl are needed to ensure that the modification is applied.


0

I guess there is no OOTB way to achieve 'Search in attachment'. With some Javascript coding you could achieve this. Create two result sources , one which queries only the Title matches and another which queries all properties and content of documents. Configure the Search results webpart to show only title matches result source. Now in the Search results ...


0

Not out of the box, but BA Insight sells a connector that supports both full and incremental crawls. http://bainsight.com/trim-connector-for-sharepoint Alternatively you could attempt to create your own connector via the BCS.


0

try to recycle the application pool where search is running. If your search servise is running under domain account (as should be), go to Windows services; find SharePoint Server Search 14 Service (OSearch14) and in properties "Log On" tab provide the correct password and restart the service.


0

Apparently, the entire search index had been corrupted. Why, we don't know. So we set about deleting the search index and run a full crawl on all content Again. But sadly, no result. Then we tried something we actually tried earlier (when the search index was corrupt). All the crawled properties that SharePoint had mapped to corresponding managed ...


0

Move the project list from the subsite to the top site and have a link to the subsite. If they can read the list they can see the data in the list even tho they cannot access the subsite.


0

OK, I can tell you what I found. First of all I am using an Online environment. I should add the mapping into the Item Display Template and was not necessary to add the mapping into the Common Body Display Template. The DIV tag, was added to the Common Body Display Template. Now the key here, is if you are configuring the Search Result Web Part to use ...


1

Any query can be "saved" as a URL. So you could create a links list that included the various queries that you expect end users to run. This TechNet article details some of the options for querying Managed Metadata fields. https://technet.microsoft.com/en-us/library/jj613136.aspx You are on the right track. You can either use the "taxid" version of the ...


0

Maybe someone will have a better solution, but for me I would create a simple SharePoint Group in your subsite, with few permissions (just for example "enumerate permissions") granted for all authenticated users. And after a full crawl see if it works.


1

The most common way would be to create your own content type, deriving from Document and add the custom column to this new content type. That way you would not run in to this kind of clashes with other OOTB content types that already inherits from Document. This custom content type could be created and published from a Content Type Hub, making it available ...


0

Try this: To remove: Look for 'PlaceHolderSearchArea' content place holder see if it's present in your custom master page. Move that placeholder to the bottom of the master page where all other hidden content place holders are. Also make sure there are no duplicates. <asp:ContentPlaceHolder ID="PlaceHolderSearchArea" runat="server" Visible="false" ...


1

Have you checked below given link for the same issue which you are having? Eventid 8031 visible every 15 minutes It is mentioned over there that you should use STSADM -o deleteconfigurationobject -id <ColumnID> I am not sure whether it works for you or not. Please let me know if it not works for you. Thanks


0

Check again if you have publish the modified page layout and the correct master page is being referred to. Still its appearing then i will prefer adding a CSS attribute in the master page to hide the small search block.


0

This is actually what makes SharePoint Search Great is that when a user is querying SharePoint, SharePoint search apply security trimming based on the user identity and permission level. This is why you will see certain user with custom permission or user with explicit permission get different result set. So the best way to do it is to start classifying your ...


0

The same issue showed up when I tried to crawl an SP2016 site with FQDN (sp.somedomain.com). The issue is not strictly SharePoint related, I saw it before with other sites using NTLM. The solution was to create a new registry entry a follows: Go to HKLM/System/CurrentControlSet/Control/Lsa/MSV1_0 in Regedit New Multistring key: BackConnectionHostNames ...


3

Stop using PATH and use Content Types. It makes requirements like this a breeze. Create a new content type based on Document. Assign the content type to the library. Optionally remove the Document content type Assign the documents in the library to your content type Crawl the content Find the content with a result source ContentType=MyContentType


0

So you have not mapped the DocumentCategories to RefinableStringxx??? I guess you should map it to RefinableStringxx (providing that DocumentCategory returns text (data type). Once you do that, you should be able to write your query as follows: path:"server-sharep/abc*" FileExtension:pdf (IsDocument:"True" OR contentclass:"STS_ListItem") ...


0

Your "DocumentCategories" must be searchable under generic keyword search, in order to use it in the refiner. Find the crawled property for the "DocumentCategories" in the search schema and then create a refinable Managed Property and add this crawled property in the mapping. Use this new managed property in the refiner webpart.


0

As far Search load balancing, SharePoint control it and Most Probably Round Robin.It really does not matter on which server you configured the query component, you can configure it on WFE or on a dedicated server. So If you have 4 Query Component on 4 wfe and only 2 WFE in LB, even then, SharePoint will route the queries on all 4 component as Round Robin( ...


3

Please don't confuse "Content Search" with a "Content By Search Web Part". SharePoint Standard does crawl and index the contents of files. Rather than use CBS web part you can use the Search Results web part to do the same thing. And YES you can get results from file shares. Also, the Video results is a misnomer. You can easily recreate the Video Results ...


1

This is likely because the trim duplicates option is enabled, trimming away similar results. Try unchecking this option.


0

Enterprise search in SharePoint 2013 is really only: Content Search Web Part Custom Entity Extraction Extensible Content Processing Advanced actions on Query Rules Video Search The differences from Foundation to Standard are too many to list separately mentioned in table given in below link. On-Premise SharePoint 2013 Edition Comparison–Search


1

Search requires that your content first be indexed by the crawler. If you just uploaded the document, odds are very good it hasn't been indexed yet and therefore won't appear in search results. Do you know how often your crawl runs? If you're running continuous crawls, you should expect to see your document in the search results within about 15 minutes. ...


1

You can implement this using metadata navigation on a document library. Enable the metadata navigation and filtering site feature, then create a document library and add a managed metadata column to it. Populate the column's terms with appropriate values (such as Troublesome Case) and then add the column to your metadata navigation. YouTube walkthrough ...


0

Search results webpart, as the name indicates gets the data from the search index. Looks like your incremental crawl is set to 15 minutes. Meaning that the SharePoint search crawler is indexing any new and updated items every 15 minutes. Search results webpart can only show the changes when the index is updated. The incremental crawl schedule can be change ...


0

I believe you can use JavaScript/jQuery to reload your page. Add a Script Editor Web Part on the page and use something like: //adjust the number to suit your need $(document).ready(function() { setInterval("location.reload(true)", 300000); });


1

Troubleshooting Tip: >= is supported only for DateTime, Integer, Decimal, Double but = is supported for Text also. Make sure the FYOWSNMBR managed property is not of type Text and belongs to one of above mentioned type. Include a space between property and >=. In many cases I have faced that the absence of space causing wrong syntax error eg: FYOWSNMBR ...


0

You have to configure your Internet URL to Alternate access mapping. The problem is due to the dedicated services farm not being aware of the AAM settings on the farm that is crawled. Fortunately, SharePoint has provided an easy solution for giving the crawling farm a hint about this, via External Resource Mapping. This below given link will give you a ...


0

1) Unless you are splitting your content into different farms, adding more processes (new Service Application) to run on the same farm (servers) will only increase the load. 2) a) Full crawl - needs to be run only when you are aware of changes to document properties. E.g. there is a requirement to add new managed properties or change existing managed ...


0

Resetting the search index completely wipes the index that currently exists. Assuming the number of crawlable items is the number you quote above, then yes, this number of items should once again end up in the index when a full crawl is complete. There may be items in the index however that have been deleted and not yet removed from the old index, or new ...


0

There are two ways to achieve #1 one is to maintain a separate "public" list of site collections and then use the results from that to drive the end user behavior you seek. The challenge is keeping the list current. Another option, one that I have used successfully, is to keep the list of site attributes on each site collection. (We provision with ...


0

1)The simple answer to your first question is that it is impossible. The reason is that Content Search is using Enterprise Search which is apply Security Trimming. So to achieve your requirements, you will need to create an application that runs with elevated privileges to return this information for you! 2) you have to create a custom display template, ...


0

That article does miss a few of the details. Here are a couple things you may be missing: The script uses 3 additional javascript libraries jQuery, Knockout and Linq.js. You'll need to download them and add references to those libraries in your masterpage. Something like this: <script type="text/javascript" src="scripts/jquery.min.js"></script> ...


0

If you are looking for subsites, you could use contentclass:STS_Web. If you want to pull site collections, you could use contentclass:STS_Site. You'd also want to include Path:{Site.URL} to pull subsites from the current site. The Search Query Tool can be beneficial in helping you craft your search queries, http://sp2013searchtool.codeplex.com. It's been ...


1

If you're on SP 2013 - Create a result source. The query in the result source should look something like {searchTerms} Status:"Open" ContentTypdId:0x01xxxxxxx ContentTypeId should be the content type for your list Configure your content search webpart or search results web part to use your new result source


2

You can use Search query Webpart for this and use filters to refine your result set. Have a look at the following link on how to configure this Using-content-search-web-part-and understanding SP2013 search


0

first, make sure that the columns/fields in question have values (Crawl won't pick or index if they have no values). Once this is done, you can either re-index the library (library settings), or re-index the site (site collection feature - search and offline availability)


0

try to use responsibleOWS:{User.Name} instead of responsibleOWS={User.Name}


0

I assume that this was a crawl issue. I don't have access to the Tenant Admin so I couldn't force an update. I came back to this later and all values were displayed as expected.


0

You say you are using the People tab. When you created your Managed Property did you select the button "Advanced Searchable Settings" and choose the PeopleIdx? This will put the property in with the other People properties and make them available (after a full User Profile Property crawl).


1

The configuration seems to be alright. Full crawl schedule is set to 'none' and for incremental crawl, you specified everything correct. If you want it to run just once per day, untick the "repeat within the day" box. If you want it to run from 9pm to 8am, keep the box ticked and set values for "every" and "for". For example: every 5 minutes for 660 ...


0

Are you under the Local SharePoint Results or are you using Local People Results? Most Search Service Applications have these content sources broken out like this, so if you are running that query on Local SharePoint Results you won't get your people results back since they are stored in the local people results content source. If you set the same query to ...


0

Simplify your life. Use a common Content Type for all 4 libraries. Then create a Result Source like ContentType=MyContent. Then apply the query to the Result Source. If you cannot create the result source then just add that query to your web part or rule. If you can't or won't create the Content Type then you can use Path, but IMHO that's yucky.


0

That is working as designed. You have to have search results to be able to "further refine" the results. The concept is to narrow down the result set based on attributes returned in the results set. No Results = No Refiners



Top 50 recent answers are included