SharePoint 2013 search list item with item id

Hi all,
I have a custom SharePoint list with many list items.
Now I like to search for a specific item in that list with the standard SharePoint item id.
Example:
If I enter in search: '1394'
Result = None
If I enter in search: 'ListItemID:1394'
Result = Success!
How can I search for the item id without typing 'ListItemID' because the user is not able to do this...
Any ideas? Thanks in advance.
Regards, Simon

You should create new Result Source.
http://technet.microsoft.com/us-en/library/dn186229.aspx
Include the incoming query in the new text by using the query variable "{searchTerms}".

Similar Messages

  • Get the Version history of a sharepoint 2013 Custom List item

    Hi All,
    I am having doubt to retrieve the field version information with the comments.
    For this field i am done like this
    1.Creating a custom list
    2.And enable versioning for the list
    3.And add a field with field type 'Multiple Lines of Text' and in the Addition Column Settings section 'select yes radio button option in 'Append changes to the Existing text'.
    4.If we done like this the changes to the list item are available outside of field control.
    Can any one help me regarding this field to get the all the versions of list item along with modified data.

    hi Asatish,
    Thanks for posting your issue, Kindly browse the below mentioned URLs to know about the fixes of this issue
    http://berg-henry.blogspot.in/2010/11/custom-list-form-with-version-history.html
    http://somnathmatere.blogspot.in/2013/10/sharepoint-2010-custom-display-form.html
    http://blog.qumsieh.ca/2009/01/29/understanding-the-append-changes-to-existing-text-option/
    I hope this is helpful to you, mark it as Helpful.
    If this works, Please mark it as Answered.
    Regards,
    Dharmendra Singh (MCPD-EA | MCTS)
    Blog : http://sharepoint-community.net/profile/DharmendraSingh

  • Sharepoint 2013 Simple List Item Approval process

    I am trying to work out how, in SP 2013 Designer to get a very simple approval process to work and I am not having any luck.
    I have a form that adds a list item for requesting the use of our corporate credit card.
    Steps:
    1) Fill out form with required info (one field is your manager)
    2) Email gets sent to manager (noted on the form) to approve or reject the request
    3) If Managers approves request > User gets email that it was approved with directions. If manager rejects request > user gets email that the request was rejected with different directions.
    4) End workflow.
    This seems so simple, but I am having such a hard time with the new interface. Please help.

    Hi Chris,
    To achieve what you need, we can follow this steps:
    Create a form  in InfoPath with the required field including the manager field which should be a person picker type, then publish it  and add these fields to the library.
    New a workflow associated with the library.
    Select Start Approval process action, and set it to start approval process on current item with Current Item: Account Id(one field of the person picker group in step1).
    Select If any value equals value condition, and set it to if Current Item: Approval Status equals 0;#Approval.
    Select Send an email action, and set it to Email Current Item: Created By.
    Select If any value equals value condition, and set it to if Current Item: Approval Status equals 1;#Rejected.
    Select Send an email action, and set it to Email Current Item: Created By.
    Make the workflow started automatically when an item is created, and publish it.
    If you have any problem, please feel free to reply.
    Thanks

  • Trying to link SharePoint 2010 Enterprise with SharePoint 2013 Search Server raises error

    Hi,
    I am currently working for a multinational who has SharePoint 2010 Enterprise Edition installed, 2 WFE SERVERS, 3 APP SERVERS, 1 DB SERVER. They also installed SharePoint 2013 Exterprise recently.
       Microsoft have recently come in and set up the SharePoint 2013 Search Server to crawl content in SharePoint 2010 as the replacement search to SharePoint 2010 Search. So they have gone through process of certificates and permissions
    setups I guess. I was told it was working, but recently failed. When I type in the search box on a web site for SharePoint 2010 I get the message:
             The search request was unable to connect to the Search Service.
    I checked the Event log and the Critical error (in Task Category:Timer) I get is the notorious: 
    The Execute method of job definition Microsoft.Office.Server.Search.Administration.CrawlReportJobDefinition (ID fa882704-80d9-415b-9b9d-eae5e9bdefd4) threw an exception. More information is included below.
            The search service is not able to connect to the machine that hosts the administration   
            component. Verify that the administration component 'e9172a05-22ec-4904-9508-
            e5431a180c2b' in search application 'Search_Service_Application' is in a good state and
            try again.
    I know administration component is the crawler. I am assuming this is permissions.
    The SharePoint 2013 Search Server is picking up SharePoint 2010 site collections items fine i.e. The SharePoint 2013 search shows items from 2010 as expected.  
    On the SharePoint 2010 central admin box the search service enabled and running (checked with powershell). (SharePoint Server Search 14)
    The Search Service id: e9172a05-22ec-4904-9508-e5432a180c2b
    I also get the message in event log for gatherer on SharePoint 2010 CA and Search Server:
           Could not access the Search database. A generic error occurred while trying to access the database to obtain   
           the schema version info.
           Context: Application 'e9172a05-22ec-4904-9508-e5431a180c2b'
    Details:
                (0x80040e09)
    Is this permissions to delete something from crawler??????
    I would appreciate if someone could help on this. I have tried to be as concise as possible.
    Thanks.
    John.

    It was a case that someone had fiddled with the Service App Associations. Hadn't ticked SharePoint 2013 search. Was still point at 2010. Thanks.
    The SharePoint 2013 Search works correctly for SharePoint 2010.
    Can someone confirm that the Search Service Application on SharePoint 2010 still needs to exist and hence SharePoint Server Search 14 Service still needs to be running? I am guessing it would as you search from 2010 interface not 2013. I am getting a critical
    error in the Event Viewer:
    CrawlReportJobDefinition (Id <SharePoint 2010 Crawler>) 
    The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component <crawler id> in search application "Search Service Application" is in a good state and try
    again.
    I think this is related to the fact we have SharePoint 2013 doing the search instead of 2010.
    Any ideas?
    John.

  • SharePoint 2013 Search: Instant Refinement of Multi-Value Properties with out clicking Apply

    Hi All,
    I will need help in modifying the Filter_Multivalue.htm file .
    The default multivalue refinement behaves as step 1 & 2.
    steps:1 When one configure a refinement as multi-value, the user is presented with the list of available filters with checkboxes
    Step:2The user must select one or more checkboxes and then click on the Apply link. After they click on the Apply link, the results are refined by the selected filters but only the selected filters are presented:
    Need solution for the below:
    Need an Instant Refinement solution, all filters are displayed all of the time and when the user clicks on a checkbox, the results are instantly refined without the need to click on an Apply link.
    Any one might have come a cross this scenairo , please share the code and details working steps.
    Thanks in advance.
    Regards,
    ajay

    Hi Ajay,
    According to your description, my understanding is that you want to make the refinement of multi-value properties without clicking Apply.
    I recommend to follow the steps in the link below to achieve the goal:
    http://stevemannspath.blogspot.com/2013/07/sharepoint-2013-search-instant.html
    With the Instant Refinement solution, all filters are displayed all of the time and when the user clicks on a checkbox, the results are instantly refined without the need to click on an Apply link.
    Best regards.
    Thanks
    Victoria Xia
    TechNet Community Support

  • SharePoint 2013 Search - Zip - Parser server ran out of memory - Processing this item failed because of a IFilter parser error

    Moving content databases from 2010 to 2013 August CU. Have 7 databases attached and ready to go, all the content is crawled successfully except zip files. Getting errors such as 
    Processing this item failed because of a IFilter parser error. ( Error parsing document 'http://sharepoint/file1.zip'. Error loading IFilter for extension '.zip' (Error code is 0x80CB4204). The function encountered an unknown error.; ; SearchID = 7A541F21-1CD3-4300-A95C-7E2A67B2563C
    Processing this item failed because the parser server ran out of memory. ( Error parsing document 'http://sharepoint/file2.zip'. Document failed to be processed. It probably crashed the server.; ; SearchID = 91B5D685-1C1A-4C43-9505-DA5414E40169 )
    SharePoint 2013 in a single instance out-of-the-box. Didn't install custom iFilters as 2013 supports zip. No other extensions have this issue. Range in file size from 60-90MB per zip. They contain mp3 files. I can download and unzip the file as needed. 
    Should I care that the index isn't being populated with these items since they contain no metadata? I am thinking I should just omit these from the crawl. 

    This issue came back up for me as my results aren't displaying since this data is not part of the search index.
    Curious if anyone knows of a way to increase the parser server memory in SharePoint 2013 search?
    http://sharepoint/materials-ca/HPSActiveCDs/Votrevieprofessionnelleetvotrecarrireenregistrement.zip
    Processing this item failed because the parser server ran out of memory. ( Error parsing document 'http://sharepoint/materials-ca/HPSActiveCDs/Votrevieprofessionnelleetvotrecarrireenregistrement.zip'. Document failed to be processed. It probably crashed the
    server.; ; SearchID = 097AE4B0-9EB0-4AEC-AECE-AEFA631D4AA6 )
    http://sharepoint/materials-ca/HPSActiveCDs/Travaillerauseindunequipemultignrationnelle.zip
    Processing this item failed because of a IFilter parser error. ( Error parsing document 'http://sharepoint/materials-ca/HPSActiveCDs/Travaillerauseindunequipemultignrationnelle.zip'. Error loading IFilter for extension '.zip' (Error code is 0x80CB4204). The
    function encountered an unknown error.; ; SearchID = 4A0C99B1-CF44-4C8B-A6FF-E42309F97B72 )

  • SharePoint 2010 search webservices compatibility with SharePoint 2013

    Please let us know whether the SharePoint 2010 search webservice is compatible with SharePoint 2013.
    When we try to hit the SharePoint 2013 search service with the query developed in the Sharepoint 2010 , we are getting "System.Not supported" exception as response from server.
    Below is the search query we are using:
    "<soap:Envelope xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\" xmlns:soap=\"http://schemas.xmlsoap.org/soap/envelope/\">"
                + "<soap:Body>"
                + "<Query xmlns=\"urn:Microsoft.Search\">"
                + "<queryXml>"
                + "&lt;QueryPacket xmlns=\"urn:Microsoft.Search.Query\"&gt;"
                + "&lt;Query&gt;"
                + "&lt;Range&gt;&lt;StartAt&gt;1&lt;/StartAt&gt;&lt;Count&gt;50&lt;/Count&gt;&lt;/Range&gt;"
                + "&lt;SupportedFormats&gt;"
                + "&lt;Format&gt;urn:Microsoft.Search.Response.Document:Document&lt;/Format&gt;"
                + "&lt;/SupportedFormats&gt;"
                + "&lt;Context&gt;"
                + "&lt;QueryText type=\"MSSQLFT\"&gt; SELECT fileName,Title,Path,Write,SiteName,URL,FileExtension,isDocument,contentClass FROM scope() WHERE CONTAINS(Path, SITE_PORT)
    and (contentClass = 'STS_Web' OR contentClass = 'STS_ListItem_DocumentLibrary' OR contentClass = 'STS_List_DocumentLibrary') ORDER BY lastModifiedTime DESC &lt;/QueryText&gt;"
                + "&lt;/Context&gt;"
                + "&lt;/Query&gt;"
                + "&lt;/QueryPacket&gt;"
                + "</queryXml>"
                + "</Query>"
                + "</soap:Body>"
                + "</soap:Envelope>";
    Please  help

    Hi Raghuramk,
    is the web service is a search query web service? if yes, i suppose sharepoint 2013 already deprecated,
    Search Query web service
    Description: The Search Query web service is deprecated in SharePoint 2013.
    In SharePoint Server 2010, the Search Query web service exposes the SharePoint Enterprise Search capabilities to client applications. This enables you to access search results from client and web applications outside the context of a SharePoint site.
    Reason for change: The Search Query web service is deprecated because the client object model (CSOM) and a new REST-based web service are available for developing Office-wide extensibility scenarios. The CSOM exposes the same functionality
    as the Search Query web service, and a larger set of functionality for stand-alone client applications.
    http://technet.microsoft.com/en-us/library/ff607742.aspx#section2
    Regards,
    Aries
    Microsoft Online Community Support
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • If Condition in Keyword Query Language (SharePoint 2013 Search Results)

    Hi All,
    Can we have an "If" condition in Query text box in SharePoint 2013 Search results page. For example, i want to hide all list items whose
    status is "HideItem" from appearing in search results?
    I am trying this: {?{searchTerms} (contentclass:STS_ListItem -ListItemStatus:"HideItem")}
    But, this hides all items like aspx pages, pdf's, docs and displays only list items. 
    Similarly, hide pages of some name like: AllItems.aspx, ViewDetails.aspx, AllAssets.aspx 
    {?{searchTerms} (contentclass:STS_ListItem_850 -filename:"AllItems.aspx")} 
    Any help would be great. Thanks in advance.

    Thanks Steve. I found this solution after a bit of struggle :).
    Also, date comparision is not working as expected. 
    {?{searchTerms} NOT(contentclass:STS_ListItem AND ListItemStatus:"HideItem" AND
    PublishDate<{Today})} is not working and throwing syntax error.
    I don't see any solid reference to KQL syntax except this msdn link.
    Can you please suggest any good material on KQL syntax ?
    Thank you once again.

  • Sharepoint 2013 search component best practice

    hi
    With a big SharePoint 2013 farm:
    2 WFE
    2 App server
    2 Search App server (havent set up these servers yet)
    What would the best way to divide the search componment between the two serarch app servers?
    Crawl component
    Crawls content sources to collect crawled properties and metadata from crawled items and sends this information to the content processing component.
    Content processing component
    Transforms the crawled items and sends them to the index component. This component also maps crawled properties to managed properties.
    Analytics processing component
    Carries out search analytics and usage analytics.
    Index component
    Receives the processed items from the content processing component and writes them to the search index. This component also handles incoming queries, retrieves information from the search index and sends back the
    result set to the query processing component.
    Query processing component
    Analyzes incoming queries. This helps optimize precision, recall and relevance. The queries are sent to the index component, which returns a set of search results for the query.
    Search administration component
    Runs the system processes for search, and adds and initializes new instances of search components.
    If you ignore the need for redunancy (we may add another 2 search app servers for that later).
    brgs
    Bjorn

    Hi Bjorn,
    According to your description, my understanding is that you want to deploy the search components in two search app servers.
    It depends on how many search service applications you need and the size of your environment.
    Here is a link about how to configure topology for one search service application with multiple search components across 2 servers for redundancy and performance:
    http://blogs.msdn.com/b/chandru/archive/2013/02/19/sharepoint-2013-configuring-search-service-application-and-topology-using-powershell.aspx
    You can also run the Query Processing component in web front server and run the other components in the search servers or application servers.
    Please refer to the link below:
    http://blogs.technet.com/b/meamcs/archive/2013/04/09/configuring-sharepoint-2013-search-topology.aspx?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+yahoo%2FZfiM+(Team+blog+of+MCS+%40+Middle+East+and+Africa)
    Best regards.
    Thanks
    Victoria Xia
    TechNet Community Support

  • Bypass content-based format detection so I can use a custom iFilter in Sharepoint 2013 Search

    Can I get SharePoint 2013 Search to bypass the content-based format detection and use the file extension to determine the format (and therefore the format handler so that I can use a customer iFilter)?
    We have a proprietary file format which uses xml, and we use a specific filename extension to indicate the type of file.  We have a custom iFilter to parse the file, because we only want some of the content to be indexed.  The iFilter works with
    Windows Search.  I’m now trying to use our custom iFilter to search the same files with SharePoint 2013.  SharePoint 2013 Search appears to determine a file’s format from its content and not from its file extension (I have confirmed this by changing
    the extensions of .docx and .txt files).  SharePoint 2013 search appears to use the built-in XML format handler to index our proprietary files.  Can I get SharePoint 2013 Search to bypass the content-based format detection and use the file extension
    to determine the format (and therefore the format handler)?  I think SharePoint 2010 may allow this, but I can’t find out if/how it is done in SharePoint 2013.
    I understand that built-in format handlers can’t be replaced by custom iFilters, but I don’t want to replace the XML format handler for .xml files.  

    Hi jeh271,
    quite interesting, because as i know iPersistStream should be installed when you need to use ifilter when using windows search.
    just curious, if you also restart the spsearchhostcontroller?
    as i know the search should have the content-based format,we cant bypass it, if we bypass it, then it may broke.
    i saw some thread about this before:
    http://social.technet.microsoft.com/Forums/sharepoint/en-US/944e6878-a7f0-4c0e-98b7-a7fb9faeef1b/bcs-connector-and-mimetypefield
    ifilter example:
    http://msdn.microsoft.com/en-us/library/hh694268(v=office.14).aspx
    last time i did this, seems similar issue:
    • The custom iFilter is working in SP 2010 but when we followed the same process of registering the iFilter in SP 2013, it was not working.
    • So, we knew that we were some missing some extra step in registering the filter in SP 2013.
    • Finally, we involved the Product group and we found out that we need to run an extra PowerShell commandlet apart from following the steps to register it in SP 2010 (given in this link:- http://msdn.microsoft.com/en-us/library/hh694268(v=office.14).aspx )
    • We ran the commandlet described here in this article http://technet.microsoft.com/en-us/library/jj219556.aspx.
    • The New-SPEnterpriseSearchFileFormat cmdlet adds a new file format and a corresponding file name extension to the search parsing system. This binds the file format to a filter-based format handler in the search parsing system. Thus, the search parsing system can only parse the new file format if the user has installed a corresponding filter-based format handler, an IFilter, for the new file format. If the installed IFilter registers more than one file name extension, the user must use the New-SPEnterpriseSearchFileFormat cmdlet to add a new file format to the parsing system for each of these file name extensions. The user must also ensure that the file name extension of the new file format is a member of the file-type inclusion list. The file-type inclusion list specifies which files that are crawled, based on their file name extensions. The system will only consider the new file format after a restart of the content processing components
    • The example for our scenario would be something like this:-
    New-SPEnterpriseSearchFileFormat -SearchApplication $ssa -FormatId dwg -FormatName DWGFiles -MimeType application/dwg
    • Then, we restarted the SharePoint Search Host controller service on the machine where you have installed the iFilter and this resolved our issue and we were able to successfully search with .dwg files using the custom iFilter.
    i am not quite sure if search treating your file as an XML file, if it is true, perhaps you can check this xmlmapper:http://msdn.microsoft.com/en-us/library/ff795813(v=office.14).aspx
    Regards,
    Aries
    Microsoft Online Community Support
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Sharepoint 2013 webDAV PROPPATCH fails with status code 409 error every time when trying to set custom property.

    Sharepoint 2013 webDAV PROPPATCH fails with status code 409 error every time, when trying to set custom property.
    anyone have any idea

    Hi
    Stumbled upon the resolution myself. The Bean Area item needs to be set to Visible=Yes in the property palette for the bean within Forms Builder, and also the implementation class also in the bean's properties must match exactly the package & class name specified in the PJC (my full implementation class string had to be set to oracle.forms.demos.runApplication).
    As this bean has no user interface component, and since the Visible property has to be set to Yes, to avoid having a random square shape for the bean sitting on the form's canvas, I also set the Width and Height properties for the bean to 0.001. This does show a very small dot on the form, but that will be acceptable.
    So in summary there has been a change for PJC / Bean Areas between 6i and 10g Forms, in 6i you could have the Bean Item to be set Visible=No, and the SET_CUSTOM_ PROPERTY built-in would work, however in 10g Forms the Bean Item must be set to Visible=Yes for the SET_CUSTOM_PROPERTY built-in to work.
    Daryl

  • Stemming not working on SharePoint 2013 Search

    We have SharePoint search enabled on our farm. There are close to 20 million items in the farm. Looking through the logs and user's feedback, we were able to find that the stemming feature is not actually working 
    When i search for "Order" i couldnt see a document whose title contains ordering in the search result. 
    This is horrible. Am i missing any thing??
    Sreeharsha Alagani | MCTS Sharepoint 2010 |
    Linkedin | Blog

    Hi,
    Stemming means that nouns and adjectives in a query are expanded to different possible inflections. Stemming essentially performs searches for words that share the same stem. Stemming in SharePoint 2013 is enabled by default.
    You can export your Search Result Web Part and Open the Web Part in a text editor, then verify whether the  value for EnableStemming is ture.
    Reference:
    http://stevemannspath.blogspot.com/2013/04/stemming-in-sharepoint-2013-search.html
    https://social.technet.microsoft.com/Forums/en-US/1e507083-0664-4c3f-b49d-b785a11960f5/fast-search-stemming-not-working?forum=sharepointadminprevious
    Best Regards,
    Eric
    Eric Tao
    TechNet Community Support

  • Office web Apps preview of SharePoint 2010 source in SharePoint 2013 search results

    Hi Team,
    We have crawled SharePoint 2010 source in SharePoint 2013 and able to get results successfully. Now our requirement is to show Office Web Apps previes of 2010 documents in 2013 search results.
    Any guidance on this please.
    Thanks,
    Manjeera

    Hi,
    Take a look at this blog post on how to do this: http://blogs.msdn.com/b/murads/archive/2012/10/11/utilizing-web-apps-2010-to-get-powerpoint-previews-of-sharepoint-2010-content-from-sharepoint-2013-search.aspx
    Thanks,
    Mikael Svenson
    Search Enthusiast - SharePoint MVP/MCT/MCPD - If you find an answer useful, please up-vote it.
    http://techmikael.blogspot.com/
    Author of Working with FAST Search Server 2010 for SharePoint

  • Office Web Apps - Preview Sharepoint 2010 documents in Sharepoint 2013 Search Results...again

    Hi,
    I found a thread in this forum With an answere to a similiar question here:
    http://social.technet.microsoft.com/Forums/en-US/28bc1e27-4a65-4c61-9b3e-cb9dad17f779/office-web-apps-preview-sharepoint-2010-documents-in-sharepoint-2013-search-results?forum=sharepointsearch&prof=required
    ...With the answere:
    "OWA uses an access token to talk to SharePoint 2013.  It cannot use this when talking to 2010.  In order to work with 2010, you have to create a custom display template that converts the file url to an openurl link. "
    BUT...
    may anyone give more information how to do this?
    Links to articles? Links to description and samples?
    jik

    Hi,
    According to your description, my understanding is that you want to preview documents from SharePoint 2010 in search results in SharePoint 2013.
    Per my knowledge, the Office Web Apps is configured to work with SharePoint 2013, so it will not work with documents in SharePoint 2010.
    I recommend to configure Office Web Apps to work with SharePoint 2010
    and make sure that documents can be previewed in SharePoint 2010 using Office Web Apps to see if the documents can be previewed in SharePoint 2013 search result.
    http://technet.microsoft.com/en-us/library/ff431687(v=office.14).aspx
    Best regards.
    Thanks
    Victoria Xia
    TechNet Community Support

  • Autocomplete is not working for Sharepoint 2013 search box.

    I added the below code in cewp in sharepoint 2010 and autocomplete worked fine.
    http://sharesilver.wordpress.com/2011/11/26/auto-suggestioncomplete-in-sharepoint-search-text-box-with-jquery-like-in-google-part-1/#comment-605
    when i added this code in sharepoint 2013 by changing the searchbox class name in the code. it is not working. why ??
    Sharepoint 2010 searchbox class name ="ms-sbplain"
    what is Sharepoint 2013 searchbox class name ?? i added "ms-textLarge" as class name but it didn't work.
    Thanks in advance.
    M.M

    Hi M.M,
    The class for SharePoint 2013 Search box input element is as follow, please check if it is what you want.
    class="ms-textLarge ms-srch-sbLarge-fullWidth ms-srch-sb-prompt ms-helperText"
    The project code you are using is updated in codeplex, and the query suggestions (similar to this autocomplete) is an OOB feature in SharePoint 2013 enterprise verison, you can take a look. 
    http://spautosuggestion.codeplex.com/
    http://technet.microsoft.com/en-us/library/jj721441.aspx
    Thanks
    Daniel Yang
    TechNet Community Support

Maybe you are looking for