This is because the web part in question is set to not show results until a search has been executed. Please enter a searchable text entry into the search box, or choose a search entry from a search list and press the "Search" button. At this point you should see the results change to data returned or a message of no items found.
This is because the web part in question has Multi-Threading enabled and the current setup of your Web.Config file won't support the amount of time required to return the data from SharePoint. See the help information under Web Part Properties for the necessary Web.Config changes.
This is because you do not have the same rights as someone else. Only those sites which you have permission to access will be presented to you.
This means that the URL you entered in the web part’s "Status Properties" field can not be understood. Please go to the Status Properties field and double-check how you specified the URL. The format of the URL must be either http://Site-URL or http://Site-URL/Sub-Site-Name.
This means that the URL you entered in the web part’s "Status Properties" field can not be understood. Please go to the Status Properties field and double-check how you specified the URL. The format of the URL must be either http://Site-URL or http://Site-URL/Sub-Site-Name.
This indicates that no lists have been found for the site and levels chosen. You should make sure that you have access to the sites you would like search and that you have entered a numerical value into the "Levels Returned" text box.
This indicates that manual administration of the shared web part property "Lists Being Returned" was attempted. Please remove and add the web part to the page and then select the lists to be returned again.
This indicates one of the following:
• The search criteria and/or filter criteria is incorrect
• The user doesn't have access to the list(s) selected
• The list or site no longer exists
• There is no data within any of the lists you have searched
To test your search text, try searching for text taken directly from one of your target lists to see if anything is returned. To test your filter criteria, try choosing a different filter field and searching for the same text to see if anything is returned.
If your search continues to yield no results, check that your target lists are populated, that your target lists and sites still exist, and that you have access to them.
This can occur for a few reasons:
1) The list must have
all of the List Template Required Fields within one of the List Templates
Supported (see the Supported Schemas
help topic)
2) The list must have been created utilizing the proper list
template.
Lists should be created via the SharePoint default list template or with a CorasWorks-generated list like Updated Contacts to be returned within the web part for selection.
No, you can name a list anything you want. However, you must make sure that your list was created with the proper list template and contains the proper fields.
The following suggestions apply to all roll-ups:
• Do not put more than one roll-up web part on a page. Since roll-ups are processed serially, adding several roll-ups to a page can cause a considerable delay in returning the page to the user, although this depends on the configuration of the web parts.
• While roll-ups can be set to pull data from an unlimited number of levels, users will experience the best performance if you configure the roll-up to look no more than 6 or 7 levels deep. As the number of levels increases, the number of sites and lists queried also increases exponentially.
• Limit the number of lists queried.
• Limit the number of fields returned.
• If you have no choice but to hit a large number of sites and lists, use CAML to filter the list before the data is returned. Collaborative Application Markup Language (CAML) is an XML-based language used in SharePoint. Pre-filtering performed through CAML reduces the number of list items received by the roll-up. You can build a CAML filter on the Filtering tab of the administration interface.
• If you still have an issue with response time, you can improve performance by selecting a specific schema. If all schemas are selected, the roll-up has to check all of them; selecting just one schema improves the roll-up’s efficiency.