I have a requirement from a client to modify the treelistex field to include a search box on top of the left content tree list box. This will allow searching of items instead of the user having to click through the content tree. This Sitecore installation has pages numbering in the thousands hence clicking through takes time and knowing where the page item exists.
How can I achieve this functionality? I will use the _system Lucene index from Sitecore to search the various items. The items need to be search based on item name, title field, content field and date fields.
Thanks
Interestingly, something just like this was posted to Shared Source the other day! Check out the Specialized Treelist from Shared Source.
Search using the built in Sitecore Lucene indexes
Related
I am trying to search catalogVersion in advanced search Backoffice. when I Type 2-3 letters of catalog code, search is not working, returning empty results.
PFB.
But when I type version , results are coming up.
This search can only search on fields directly on the object you search. You cannot search on fields of a sub-object. In this case, you want to search on the catalog.name but that's available through CatalogVersion.Catalog.name, so one level to deep to search.
While Staged is directly available on CatalogVersion.version, so you can search on that.
With the out of the box, you could click on the ... and in that field search for your specific catalog. Then it will be selected in this search box
We use the search feature in the Extension Library Layout control to search a view. It works as expected. But we wold like to expand that search.
The documents in the view each could have one to many "comment" docments. The documents are displayed on the issue xpage with an "embedded" view. The comment is associated to the issue via the parent's UNID. There is a parentUNID field on each comment but the comment document is not a traditional response document.
We would like to be able to search all issues and their comments without having to display the comment in the view. When the search is performed, we want only the issue document to display in the view.
Is it possible to expand the search (with out creating my own search box) to search the comments as well as the issues? If so how would I do that?
A repeat control may be the best way to do it. Then you can search a view containing both. For each row, if the document's Form is an issue, display that. If it's a comment, get the "parent" and display the values from that.
You might want to make each row contain a Panel, so you can attach a dominoDocument datasource for each row containing the documentId of the issue (remembering to set ignoreRequestParams of course!)
I've created a custom content item. I also have a projection which filters the content items (e.g. on a tag or something else).
I've installed the Modules: Search, Indexing and Lucene but when I search for an article I don't seem to find any of my custom Content Items.
How can this be done?
I'm using Orchard 1.5.1
Nevermind.
After installing search the "Index this content type for search" was not directly visible on my custom Content Item.
The field appeared when I added another Field to my Content Item and saved it.
That is the reason I could not find or select it :-)
I am trying to create a Page Layout, that should have a lookup field. Lookup field should always get populated with a list's items.
This list will exist in all subsites, so whereever I create this page, list should get populated with listitems from current site.
I tried using site column lookup field, but it always point to list under top site and not the current site.
Any suggestion on how to make it work or better alternative? Thanks!
Let me know if I can provide more info.
The most straightforward solution I can think of is using a cross site lookup column and creating a seperate fields for each subsite. However, you will need to create and use different Page Layouts for each subsite.
You can use http://sp2010filteredlookup.codeplex.com/ for cross site lookups.
Solution 1 - Use http://sp2010filteredlookup.codeplex.com/
Use filtered lookup solution. So let's say you have your custom Page Layout and custom Page Content Type.
Every time you create new subsite, you should remember go to Pages list settings and edit Page Content Type by adding cross site lookup (with the same field "internal name").
So you still have one Page Layout (and one Content Type). But for each Pages library instance, Content Type contains diff fields (but with the same Internal Name). It will allow you run CAML queries and other things needed without any problems.
Solution 2 - develop custom sharepoint field type.
In edit mode, control will render "dropdown list" and populate data from list instance that is on current subsite. In the field settings you can have relative list url.
Solution 3 - hidden text field / js snippet solution
Page Content Type can contain hidden text field (it can contains selected field value in json format for example). Develop js snippet that will handle all the logic (rendering in edit/view mode, saving etc) and put it on Page Layout (aspx).
I would suggest to use solution #1 or #2.
I set up a new scope and passed in the URL for a specific document libary that I created that hold 2 word documents.
For some reason when I start a full crawl, it does not see the 2 word documents.
The word documents have meta data and I've created Managed Properties that map the crawled properties.
I am trying to utilize the Advanced Search webpart to be able to search from this scope. When I enter a search term such as the filename of the word document, no results are returned.
Any ideas?
You need to enable the document library to be searchable. Enable it through the document libraries properties.
Edit
See Harnessing Properties in SharePoint Search
To get to the Document Library Advanced Settings page, from within a given library, select the Document Library Settings menu item from the Settings dropdown, and then select the Advanced settings hyperlink under the General Settings header. Somewhere in there, you should see something like the following image. Make sure that the radio button is set to Yes. Source
(source: bamboosolutions.com)
What account is the crawler running as? Maybe that account doesn't have read permission on the list, so it can't index it.
Can you find information from the same documents in other document libraries, when using the default search scope?
Can you find information from this document library using the default search scope?
Are you trying to create a custom search results page, or just scope?
One thing to try is to check the search crawl log to see if there were any errors when it was searching the library.