Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Using a Roll up web part in V3.0 with MOSS 2007

  Asked By: Melanie    Date: Feb 25    Category: MOSS    Views: 2594

I am running V3.0 with MOSS 2007. I have several subsites. I want to
simply create a list in one of those sites, and be able to view that
list in another subsite or several subsites. Example: I want to create
a simple contact list with two fields: Name, and Phone Number. Next I
want to show that simple list in another subsite, or maybe in several
subsites. I have read about Rollup webparts in MS V3.0 but can not
find one. Perhaps its called by another name.

Any ideas? This really simple thing has got me stumpted and causing me
great trouble.

Share: 

 

22 Answers Found

 
Answer #1    Answered By: Sierra Lewis     Answered On: Feb 25

Depending on the site template you used, you should have the Content by
Query web  part available. In addition, you can use a Data View (created
using SharePoint Designer) to do this using the Lists web service as
well.

 
Answer #2    Answered By: Dwight Becker     Answered On: Feb 25

I did try to load the Content by Query web  part but it said it could
not work in the site I am using. I don't know what that means, and
have done research on it. I've found nothing to make it work yet.
The Data View created by Designer will only let me look at lists in
the current site, not in any other site.

I was once told that MS did have a Roll UP web part  that allowed you
to view any list or library no matter where the site was, even if it
was another site accross the world.

I'm at a loss so far.

 
Answer #3    Answered By: Amar Kumbar     Answered On: Feb 25

Sounds like the site template used to create the site doesn't support
the CQWP - it requires features that are not available on all site
types.

Data Views will allow you to connect to sites on other lists, but (as I
said) you need to use the Lists Web Service to create a connection. The
automatic connections in the SharePoint Designer are indeed only for the
current site.

 
Answer #4    Answered By: Marc Dixon     Answered On: Feb 25

Here is what I get when I load the web  part:
"Unable to display this Web Part. To troubleshoot the problem, open
this Web page in a Windows SharePoint Services-compatible HTML editor
such as Microsoft Office SharePoint Designer. If the problem
persists, contact your Web server administrator"

When I open the page in designer and click on the web part  it tells
me the XSL file can't be found.

I am using the template for a Team Site, the most common site there
is, I would think. I should work.

I don't know how to use the "Lists webservice" you speak of, if that
is what's needed to make the data view webpart work accross the site
collection.

 
Answer #5    Answered By: Johathan Mcgowan     Answered On: Feb 25

I just found out that the CQWP can only be used if you created your
site with the Publishing Features activated. MS says that when you
create a Team site, the Publishing is desabled. To enable it, you
can go to Site Features. I tried that but then get a message that I
need one or more features turned on. Yet, Publishing is the ONLY
feature I did NOT have turned ON. It's a round robbin now. Why
couldn't the message tell me WHAT features it is lookinf for to turn
on, for crying out loud.

 
Answer #6    Answered By: Georgia Barr     Answered On: Feb 25

Turn on Publishing Infrastructure for the Site Collection and then
Publishing for the Site.

 
Answer #7    Answered By: Jessi Sweet     Answered On: Feb 25

Actually the DVWP will let you access information in other SharePoint sites as
well. You need to click Connect to another library in the Data Source Library
and then supply the URL of the other site(s). This can be used to connect to
the parent SharePoint site or a different SharePoint site.

 
Answer #8    Answered By: Kelvin Mckinney     Answered On: Feb 25

Turn on publishing for the site 'collection', then turn it on for the site.

 
Answer #9    Answered By: Gaurav Ghosh     Answered On: Feb 25

I tried that, but even on the TOP SITE of the collection, it still
tells me that I need to turn on other featurs first. Another round
robbin, I'm afraid. MS just leaves me hanging. If they took the time
to write that message, why couldn't they tell me what other features
I need, even if it is an example.

 
Answer #10    Answered By: Katelynn Donovan     Answered On: Feb 25

I believe it also needs enabling at the root level - it's hierarchical.

 
Answer #11    Answered By: Geraldine Slater     Answered On: Feb 25

Not the top site, the site collection. If you are a site collection
administrator you should see a "Site Collection Features" section in
Site Administration where this can be done. If you are not a site
collection admin, you will need to find someone who is.

 
Answer #12    Answered By: Gail Richmond     Answered On: Feb 25

we have exactly the same requirement, and have been fighting this for 1-2
months at 2-3 hours/day, finally succeeded. (MOSS site).

The content query web  part (CQWP) can do it. It is a PAIN to get columns from
your lists other than the "default title", BUT, it can be done. There are
quite a few good blogs on the subject. The advantage of the CQWP is you do not
have to specify the lists nor the sub-sites if you use content types. To use
the CQWP, the "publishing feature" MUST be activated. Typically this is not
done for, say, "team/collaberative" sites, but, no problem to do so.

Alternatively, you can build a DataView using SPD which links specific lists
(from any sub-site). The main problem is you have to edit/modify the linkage
everytime you add a list.

 
Answer #13    Answered By: Ramona Solis     Answered On: Feb 25

can you share how you got the CQWP to show anything other than the
default title?

 
Answer #14    Answered By: Harvey Blankenship     Answered On: Feb 25

Do I recall correctly that the publishing feature first has to be
enabled in central administration to be available at the site collection
level? Perhaps under application management (manage features or
something like that?). It's been a while since I've been in there-this
is from dust-covered memory.

 
Answer #15    Answered By: Xiomara Blanchard     Answered On: Feb 25

Publishing Infrastructure has to be activated at the Site Collection
level and Publishing at the Site level. Neither is in Central Admin.

 
Answer #16    Answered By: Rosemarie Cervantes     Answered On: Feb 25

I managed to get two things working; ContentQuery Webpart, and the
DATA VIEW Webpart. Here's how;
1. CQWP - As Paul said, be sure you have permissions to activate the
Publishing feature on the Site Collections (I did have). Go to the
Top Site in the collection of subsites under it, Click Site Actions,
Site Settings, Modify all site settings, then look for Site features
under the heading "Site Administration" - Click Site Features, then
you will see a whole list of items there; find the one that
says;Office SharePoint Server Publishing. Activate that. Then go to
the site where you want to add the CQWP, and drill down to the same
area as above and activate Office SharePoint Server Publishing
feature. Then, edit the page where you want to place the CQWP, click
on ADD web  PART on the zone you want, then look for ContentQuery
webpart in the list, and select it. The rest is making it work
properly.

2. Adding a DATAVIEW webpart. You can only add this using Designer7.
Now here's the secret - you can not add a DATAVIEW webpart to a
ZONE. You must find a place outside the ZONE, then it will let you
drop it in. Once you have configured the DVWP and completed
everything. then and only then will you be able to drag it into a
ZONE. That's what I've been fighting all this time. I did not know
you had to start the thing OUTSIDE the zone ,then after you've
finished with it, you can either leave it there, or drag it to a ZONE
and it will let you do that.

I hope I have not confused anyone. SOme of you had the answers but
unfortunately for us dummies, you left out crucial steps you most
likly thought we knew.

 
Answer #17    Answered By: Manan Kadu     Answered On: Feb 25

Does activating Publishing Infrastructure at the Site Collection level
create by itself any changes in behavior for existing subsites? Does
activating Publishing at the Site level create by itself any changes in
behavior? Or do those features simply enable new functions which _can_ be
used?

 
Answer #18    Answered By: Tonia Franco     Answered On: Feb 25

They just enable new functions to use, and you will see new web  parts
available as well. My site runs no differently before or after I
enabled the Publishing feature.

 
Answer #19    Answered By: Amareswar Karkera     Answered On: Feb 25

There is one major difference. With Publishing enabled the option to
save the site as a template will be hidden, and any templates you might
create via the various workarounds floating around on the net are likely
to fail in a variety of possible ways.

 
Answer #20    Answered By: Cheyenne Jacobson     Answered On: Feb 25

There are 3 or 4 good blogs on obtaining more columns than the "title" one.
The following is one of them:
http://paulgalvin.spaces.live.com/blog/cns!1CC1EDB3DAA9B8AA!491.entry

 
Answer #21    Answered By: Makayla Lewis     Answered On: Feb 25

I reviewed those sites and they indeed do give details on how to
customize the CQWP. However, I will have to spend lots of time
figuring it all out, which I don't mind, but my boss does. I'm not a
HTML programmer, or any kind of programmer by trade. I was hoping that
the CQWP had more granularity built in. I saw a demonstration of the
CorasWorks and Bamboo solutions RollUP web  part and it has a GUI that
allows neophytes like me to work it. And they have a good deal more
capabilities built-in that customizing the CQWP would take me a great
deal of time, even if I did know what I was doing. So, I'm going to
look into those web parts, if I can get my boss to spring the cash for
it.

 
Answer #22    Answered By: Miranda Scott     Answered On: Feb 25

we are in the same boat and likely to go with the Bamboo rollip WP, but
I need to present my management with alternatives. For us, it is not the $$,
but getting it approved through the IT red tape. Call if you wish to discuss
any CQWP details that we may have uncovered.

 
Didn't find what you were looking for? Find more on Using a Roll up web part in V3.0 with MOSS 2007 Or get search suggestion and latest updates.




Tagged: