I have googled this and seem to only be able to find the same Tutorial here or variations thereof. I have two lists. Each one is on a different site. I need to make a list/view joining these two lists. One site contains basic employee data, (such as department) and the other site contains details about that department that we need to show on a high level overview of employee data.
It's sharepoint 2007, two sites, same collection
I used this tutorial.
He mentions "Please note: If your lists are on another site collection you will have to use the Connect to another library... link" and he includes a screenshot.
Aonther way to go is to roll your own field type and make it similar to a lookup field but instead make it go fetch data from a list in a different sitecollection. I don´t have ready example of something like this but this post atleast explains how to go about constructing a custom field type.
I would use Sahil Malil's technique. However this is much the same as the link to Microsoft that you've already given. Why doesn't this do what you need?
Here are a couple good places that have worked for me.
Connect to Another Library in SharePoint Designer 2010
Displaying a SharePoint List from Another Team Site
Related
I have around 300 Reporting Services reports in SharePoint 2013, total, in ten different folders (by department), but my sales team's folder has around 100 of those and they find it difficult to remember which ones they care about and quickly navigate to them. Is there a way they can easily set up a list or some sort of page within SharePoint that points to the reports they care about?
You can tag/index your documents and then create a list and a view to that list that show documents that are indexed with a certain tag. For example shows only documents that contains the tag "important"
Create a Document library and add Document link content type. In this way you can manage the links on different views.
You can use metadata while making any entry in a list. So when you are creating any list make a use of that metadata and show only those list items which contains that tag.
Please correct me if i understand your question wrong
Thanks
I have a document library set up with multiple different categories of document, and I'm using a metadata column to differentiate between them.
I want to be able to display two different document library web part on a page for different categories of file side by side. This is simple for one category, I just set up a list view filtered by the metadata column, but when I add a second web part alongside the first, it breaks the first one.
I have no idea why this is happening, but it seems like SharePoint isn't happy with pulling two sets of data from the same document library.
When I am editing the web parts, I can get them to both display the documents I want, but then when I click save, the first web part empties.
Not sure what other information would be useful for diagnosing or helping with the problem, so if I haven't given enough detail let me know. I am familiar with SPD as well as developing through the web interface, so if this needs a more complex solution that's fine with me!
Having spent some more time playing around with this, it struck me that I could probably achieve what I wanted using something other than a Document web part, and I was right.
Instead of using the somewhat inflexible document web part, I created a content query web part which only searched within the document library from my site, and filtered by the metadata column.
This way I can create as many queries as I like and they don't interact with each other in weird ways. It also has the advantage of being significantly easier to customise the output without needing to resort to SharePoint Designer.
Content Queries are the answer!
I've got a tricky situation I'm trying to determine the best way to solve. I'm a VS developer who is learning SharePoint so it's a little frustrating to me when what I am trying to accomplish could easily be done with code and a db.
I have three lists, a parent and two children list that are linked through lookup columns. The client actually wanted everything in one list but due to SharePoint column type limitations I had to split the data into the three lists, there are over 300 fields. The client wants to see all the lists together in one view and be able to filter and edit groups of items.
I have successfully created a new data source linking the lists and can display that on one of my pages to view. After some research however I have learned that I can't create a datasheet view from this linked view due to limitations in the Office componets that SP uses. Which makes sense.
The business need is for the client to filter the three lists based on criteria they select from either list A AND list B and list C to get a group of items, they make the updates and save the changes back to the 3 lists. They prefer to do this in datasheet view because this mimics the excel spreadsheet that they are currently using that this website will replace. They will potentially be updating between 1-30 items at a time using this, which is why they prefer the drag and copy functionality.
I was thinking of two options: trying to create some kind of custom web part that has a gridview of all the columns in edit mode that they can filter down to their items and make their changes. Then I would have to loop through the fields and make updates programmatically. I also saw on this site jQuery.sheet, that looks like it may be a good solution if I go this route instead of gridview.
Or have a modal window with the columns listed, have the user select what they want to filter to, then redirect to a page that shows the three lists in their own DSVs. The user would have to make updates in the three separate views. Then I would use workflows to synchronize the lists after they had made their changes.
I always end up trying to do things programmatically since I am still largely unfamiliar with SP and only seem to hit its limitations instead of its strengths. Has anyone tried to do something similar to this? Or do you have any suggestions as to the best way to accomplish this? Best practices? I appreciate all thoughts and comments! FYI I've also posted this on the MS SP forums as well to cast a wider net...
Thanks,
Sabrina
In this case, you are better off going with a custom solution. A webpart would be an excellent choice for delivering your custom interface.
A dataview webpart will do the job, but if you feel comfortable with the jQuery solution it would make for a nicer interface.
In your code, treat the lists as you would a database and isolate it from the logic and interface code within the webpart.
We want to create a common document library on a certain site level and then create views on that document library in the different sub sites?
Is that possible in SharePoint?
Can it be done declaratively?
Rine
I would recommend to use the DataFormWebPart (requires SharePoint Designer to insert and customize the DFWP, the result can be exported to a feature)
The following blog entry lists a suitable SPDataSource sample:
SPDataSource and Rollups with the Data View
Good Luck!
Not out of the box. You will either need a third party "roll-up" ("roll-down") web part or you will need to write your own. OTB, views for lists/libraries are only visible at the current site level.
That being said, roll-ups (in one form or another) are probably one of the most common 3rd party seller for sharepoint (just a guess). In fact, I would bet there are several free projects out there that you could use (Check codeplex). You should have no problem finding one that meets your needs.
My suggestion would be to write your own, as this would give you some real good experience using the SharePoint object model and there really are no complicated concepts. Once you get past being able to do site navigation and accessing list data through the OM, you pretty much have all the tools you need.
Good Luck
I have found a cheep and great webpart which does a documents rollup from all subsites with search, paging and sorting functions.
http://speasysolution.miiduu.com/es-sharepoint-2010-documents-rollup
i used it, its simple and powerful
This should be a really really simple thing, but for some reason it is just eluding me.
I want a Sharepoint page which will have a drop down list that is tied to a database lookup table.
When an item is selected and they click a GO button, I want it to update a gridview that is also on the page.
I'm looking for a simple how to - while assuming I'm a sharepoint idiot. BTW, I am using the Microsoft Office Sharepoint Designer.
Thanks,
Edit:
My need is actually very simple. I want to filter the results of a query using a drop down list. This used to be called a master - detail relationship.
For example, my regular data has school name, application name, and how long the application was running. Because there could be a hundred applications per school and there are 60+ schools, I only want to show one schools information at a time.
So, I want to put a drop down list at the top of the screen which contains the list of schools. When one is selected, the gridview should be updated to reflect the new schools information.
Chris.
I currently use a drop down tied to one sharepoint list to filter a dataview of another sharepoint List.
The instructions are here:
http://blogs.msdn.com/sharepointdesigner/archive/2007/03/05/asp-net-controls-filter-the-data-view.aspx
I'm not exactly sure of the specific needs here, but it seems that you are trying to stretch a bit beyond what Sharepoint Designer is well suited to. To look up data, you do have access via the dataview web part, which is here:
http://office.microsoft.com/en-us/sharepointdesigner/HA100948041033.aspx
However your filtering needs may prevent you from using this. If you want to do it .net without knowing too much about MOSS, you can use the "son of smartpart" (google it) which allows you to host standard .net user controls in webparts.
Hope this helps!