Tag Info

New answers tagged

2

The answer would be Item Display Templates. You will need to convert your custom Abstract Column to a managed property and create a custom item display template which displays this managed property for your search results. Here is good post on how to turn your own custom column to appear in search results. ...


0

I've had pretty much the same requirement for a while now and agree with Matt for the most part. If you can then ideally move suitable files (e.g. office docs, not binary files such as exe, msi etc.) off the share into a document management system, such as SharePoint and archive off any legacy files. This would typically be a reasonable sized project and ...


2

You are on the right track, make sure you do a full crawl to populate the index with the managed properties. You need to do this anytime you make changes to the managed properties, adding crawl properties or adding new managed properties. The items starting ows_ are crawled properties and you can map multiple crawled properties to a managed property. These ...


0

You managed property needs to be Queryable and Retreivable. https://technet.microsoft.com/en-us/library/jj219669.aspx#MP_Overview


0

Sorry @drag - but it is looking like you may have an issue with the site collection itself. I would backup and restore the site collection to a new location (new URL) in the same web application but with a new Database. If that works - consider removing your current site and re-add from the same backup procedure into a new database. If you hit errors in ...


0

I agree with James, but to add a bit more advice: Someone has to take ownership of permissions. One technique is to create a new top level folder and as you determine the content is either "safe for search" or needs security, move the content to the new folder and apply the necessary permissions. You can try to search for terms like "password", "salary" ...


0

Crawling another SharePoint as content source is possible in all versions, as outlined here: Use content sources effectively When you create a Search service application, the search system automatically creates and configures one content source, which is named Local SharePoint sites. This preconfigured content source is for crawling user profiles, and ...


0

So SharePoint has IIS setup to recycle application pools at around that time. I would suggest that is why you are seeing the behaviour. To check go to the server running search using REmote desktop. Open up IIS console, expand the server node and choose application pools. Select the search app pool and choose recycling settings in right hand pane. Check the ...


0

Certainly late to the game here, but for the benefit of anyone else that stumbles across this page, you can use the following to reference a Managed Metadata column called MMSFieldName in the CSWP: owstaxIdMMSFieldName:{Page.MMSFieldName} The reason for this is that the token is transformed to the GUID (TaxID) rather than the plain-text label value. In the ...


1

In my opinion - if there's a risk of passwords being in that store, then do not crawl it. It doesn't matter who decides to have the responsibility, or who dodges it - if that risk is there the mitigation is not to crawl that store, and just to use whatever new file storage/sharing technology you decide to go with (File shares, SharePoint, OneDrive for Biz, ...


0

Here is the 2007 solution, think it should work for 2013 as well: http://blogs.technet.com/b/sushrao/archive/2009/03/26/microsoft-office-sharepoint-server-2007-moss-403-forbidden-error-when-clicked-on-search-settings-page.aspx


0

I don't think you need a full crawl. This Microsoft Support article only mentions the compiling/update, but does not mention a crawl. Search scopes and their rules are compiled on a schedule that is adjusted automatically based on the frequency of past updates. The administrator can also set scope updates to occur manually. A new scope will not ...


0

After creating the Enterprise Search Center I changed the setting in my Intranet by entering a Search Center URL and results page URL and now it's working. Thx for user19952.


0

Ideally when we mention path in Content Search Web Part, it brings through result from that site and its sub site OOB. we don't need to do anything extra on top of it. 1. If your requirement is to bring results from Web1 and from its sub sites, then I believe below simple query should work. path:"http://site/web1" 2. If you would want to bring ...


0

Here's a script I've used that works for me in IE8. It works best in IE8 with jQuery version 1.8.2 in my case. $(".srch-Title3 a").click(function() { href = $(this).attr("href").toLowerCase(); if (href.indexOf(".pdf") !== -1) { window.open(href, "_blank"); return false; } });


0

thx a lot. Though it does not search multiple text from search box ? Example if I type : sharepoint asp.net.. it will only search for sharepoint write ? How to fix this ? Thank you


0

This is a SharePoint Bug. It seems to be fixed in the October 2014 CU, I couldn't find any details in any KB article though. I installed the May 2015 CU on a SharePoint 2013 SP1 patched server and the problem is gone.


0

Check if the list contents are enabled for searching. Go to List Settings --> Advanced Settings and see if Allow items from this list to appear in search results? is marked as "Yes". Also, make sure that Search Service Application in Central Admin is crawling your content.


1

When crawling, SharePoint Access all the pages like a normal user does. You can´t avoid that. What you can do is to check if the current request to the site is coming from the crawler SPUtility.IsSearchRequest(this.Page.Request); and handle that request separately (eg Rendering and doing nothing at all if there is no Need the crawl the Output)


1

I found a solution, a litte stupid but it works I add javascript to get user's photo from mysite <div id="UserOWSUSER" class="ms-peopleux-userImgDiv">Nom : _#= ctx.CurrentItem.UserOWSUSER=#_</div> <!--#_ var UserData = ctx.CurrentItem.UserOWSUSER; var UserNumber = UserData.indexOf("@"); var ...


0

Microsoft failed to include IE11 browser support even after SharePoint 2013 SP1 The fix is to run the site in compatibility mode until SharePoint officially supports Internet Explorer 11. Or install IE 10. or try this workaround


1

In SharePoint 2013 it is called a thesaurus. You can import it using Powershell. See MSDN for more details.


0

You can do all this by customizing the Display Templates. Every result type has it's own display templates. That you can find inside /_catalogs/masterpage/Display Templates/. So make sure you take a look at below given links. Here is the thing you are looking for: Introduction to SharePoint 2013 Display Templates Creating customized search results in ...


0

Here you can see how SharePoint is looking up the value for "Today" private static string GetTodayValue(string token, IReadOnlyPropertyCollection queryProperties) { string parameterNameFromToken = QueryTemplateHelper.GetParameterNameFromToken(token); DateTime dateTime = DateTime.Now; if (queryProperties != null && ...


0

Thanks for the information, Acrobat changes w.r.to browser also needs to be changed other than SharePoint, Please follow the below link This includes enabled and disabling the adobe ad-on which will enforce the pdf documents to open with a specific program.


0

You need to enable the client Intergration feature. In SharePoint Central Administration site, click Application Management->Manage Web Applications, select the web application for the site. Click Authentication Providers, select default zone, and select Yes for "Enable Client Integration?" read more over here: Configure SharePoint Server to Open Office ...


1

You can create your own by using the Search API (or REST) to look at Query Suggestions. https://msdn.microsoft.com/en-us/library/office/dn194079.aspx


0

If you are looking for reverting back your changes then, I guess resetting the page layout to its Site Definition can help. 1. Open your site in SP Designer 2. Click on Page Layouts tab on left hand menu 3. Select the SearchResults.aspx 4. From the ribbon control, in Actions section, click on Reset to Site Definition button. This will revert back your ...


1

If you have the excel Service enabled then this problem is most probably with ASP.NET Impersonation. Solution: Disable the ASP.NET Impersonation at the Server level and "SharePoint Web Services" level. Via: IIS > Authentication > ASP.NET Impersonation -- Microsoft Knowledgebase entry IF no ECS configured in the farm then check this


3

Is this behavior for all users or only few and what about browser? In the real world scenario it should work, just make sure the Enable Client Integration at web app level. Central Administration > Application Management > Manage Web Applications > select the web application > Click Authentication Providers > select default zone, and select Yes for ...


0

Start by checking the Content Source and the line that begins with SPS3:// that should be a valid Web Application in the default Zone. Next check your Alternate Access Mapping for the My Site Host. Often this is the problem. If it is none of these please comment and provide the URLs for all of the above. (Or at least examples.)


0

Please make sure search service application is running.


1

Null root directory is OK, it designates the default index location. Once you for example relocate the index, it will be assigned the new directory name. Logically, to restore the default index location, you can run New-SPEnterpriseSearchIndexComponent commandlet without having to specify -RootDirectory property.


0

I found the solution. If you define in the KeyWordQuery Object SelectedProperties, than you get beside these Properties additional Properties so that a result via result[0] is not possible. You have to call the Property explicit by result["Title"]


0

You can do this by modifying the search navigation in the web you are in to point to a custom results page. It would look something like: {SearchCenterURL}/contextresults.aspx?ctx={contexturl} Where contextresults.aspx is the custom results page you have created in your search centre. Edit the search results web part on the custom page and select Change ...


0

Something based off whats here already, but put together fully for how I needed it and in case anyone else needs this. Where a start date is blank or before now and an end date is blank or after now is as follows. -EndDate:1900-01-01..{Today} -StartDate:{Today}..3000-12-31


0

Unfortunately this can't be performed. Crawling can't handle a site mailbox. Only Exchange Server Public Folder can be crawled with a Search Service Application in SharePoint 2013 Server. Reference: Site Mailbox Search


0

I found the information I was looking for. I was missing permissions for the service account that was performing the work. Specifically, the missing permissions were "Log on as a service" and "Replace a process level token." I found this blog post to be quite helpful in figuring out my issues. I should also note that due to particular Group Policies in ...


0

When you say your custom property is blank, you mean when you look at the result of the Search Results template using your modified Display template ? It may seem far fetch but have you tried "Using a single template to display items" and specifying the modified template in the Search Results Web part configuration?


2

That is how crawl works. If you have PhoneNumber in these format: 1234567890 1234 567890 123 4567 890 123 456 7890 When crawling, every sign or space " ", "-", "_", "(", ")" is like delimiter and it is putted in new place inside array. For example: for 1. it will be array[0] with (1234567890), for 2. will be array[0 and 1] with (1234 and 567890) ...


2

Should have waited 10 min with that post.. $ssa = Get-SPEnterpriseSearchServiceApplication -Identity "Search Service Application" $scope = Get-SPEnterpriseSearchQueryScope -Identity SomeScope -SearchApplication $ssa $scope.Rules $rule = Get-SPEnterpriseSearchQueryScopeRule -Scope $scope -Url http://sp2013 -Identity 3 $rule.MatchingString = ...


1

Filter out all The queryable managed Properties from this list and you have all the default ones: https://technet.microsoft.com/en-us/library/jj219630.aspx Then there are all the autogenerated ones, which you can get my listing all queryable properties in you environment, UI or PowerShell.


0

Set the default search value for that page to a value that can't be true.


0

As per my experience and recommendation.When you configure a new Search Service application and/or create a new content source then. You have to run the full crawl and followed by incremental crawl. Once it create an index then you can enable the continuous crawl. As you said, you did not perform the full crawl on the content source then SharePoint ...


0

I have done some extensive research on this topic a few weeks ago because I had a similar requirement on the project I worked on. Even though you can setup crawl rules that exclude subsites, you cannot setup conditions to take page X is not published into account. What I ended up doing was creating a TimerJob which ran a couple of times a day (based on how ...


0

Copy the existing display template: go to https://your-server/_catalogs/masterpage/Forms/AllItems.aspx copy Item_Person.html and rename it After this, open your copied file and check whether uPicUrl is empty. If yes, provide it with your default URL. Now, you have to create new Result type. Go to Site settings -> Search -> Result types. Find 'Person' ...


1

Copy the out of the box Display Template, rename it and upload it back to SharePoint. Edit the Display Template to point to your desired image. There are many answers to this process here in SE as well as blog posts on the topic. You just have to create a new Display Template.


3

In Central Administration navigate to your Search Service Application (Central Admin > Application Management > Manage Service Applications). In the Search Service Application, navigate to Crawl Log and select “Host Name” in the links at the top. Select the Host name URL where your page exist and paste the URL to your page in the search box below the text ...


0

.NET has a feature to identify browser. I think you might be able to solve your issue if you update your sharepoint servers. You might be able to verify before by switching setting IE in compatability mode to 9 and back. If you see that it is working on, then give it a try.


0

Have you tried going through a Technet or MSDN link ? Tryi this link MSDN hope this helps you out..



Top 50 recent answers are included