none
Items Matching a Tag - limited to 50

    Question

  • I would like to use search to get all the items that are tagged with a specific taxonomy term, such as Hospital, as people don't put "hospital" in their title or filename.  So when I search for Enterprise Keyword "Hospital" the results that show up are only with those containing "Hospital" in the title, subject, or filename.  I have specifically placed "Hospital" as a tag and then would like to search for it, itself.

    I tried to do so with the Search-Drive Content webpart, for Items Matching a Tag.  "AWeSOME" I Thought, JUST what I want!  I can create a page and then have the content search "display" my results.  I can create a LOT of pages for multiple "Hospital" "Ambulance" "ER" etc.  SO EXCITED!  BUT It doesn't seem to be working right and or I am limited to 50 items.

    What could I do to make this a reality?  If search is NOT the answer, that is fine, however I thought that Enterprise Keywords and Search go hand in hand, so I thought that there might be something that I can do!

    SharePoint 2013 RTM Enterprise Edition dec 2013 CU

    THank you!

    Monday, January 06, 2014 7:53 PM

Answers

  • Hi Matthew Carter,

    regarding this issue, is by design, if we change the limit more than 50, then it will make your environment unstable, and we can't support for the result if the changes is made.

    Under Display Properties, in the Results Per Page box, type the number of results that you want to appear on a page before pagination is required. The maximum is 50 results. The default is 10 results. Increasing this number affects how quickly the user interface renders.

    http://technet.microsoft.com/en-us/library/gg549981.aspx

    as i know if you are using sharepoint search, this search is not as robust as FAST search, there are some differences in the indexing, for example, when we gather the result the hard limit is 500 items, it should be seperated to different pages. if the items should be more than 500, lets say 600, so if will index the first to 1~499, then when you select the other page then it will render the rest. so if we change them to more than 50 items it may effect the indexing matters, and it will make your environment performance goes down as well.


    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.

    Monday, January 13, 2014 8:29 AM

All replies

  • Hi,
    For this issue, I'm trying to involve someone familiar with this topic to further look at it.
    Thanks,

    Jason Guo
    TechNet Community Support

    Monday, January 13, 2014 7:49 AM
  • Hi Matthew Carter,

    regarding this issue, is by design, if we change the limit more than 50, then it will make your environment unstable, and we can't support for the result if the changes is made.

    Under Display Properties, in the Results Per Page box, type the number of results that you want to appear on a page before pagination is required. The maximum is 50 results. The default is 10 results. Increasing this number affects how quickly the user interface renders.

    http://technet.microsoft.com/en-us/library/gg549981.aspx

    as i know if you are using sharepoint search, this search is not as robust as FAST search, there are some differences in the indexing, for example, when we gather the result the hard limit is 500 items, it should be seperated to different pages. if the items should be more than 500, lets say 600, so if will index the first to 1~499, then when you select the other page then it will render the rest. so if we change them to more than 50 items it may effect the indexing matters, and it will make your environment performance goes down as well.


    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.

    Monday, January 13, 2014 8:29 AM