Re: WSS 3 Calendar - Connecting to Lists

Tech-Archive recommends: Fix windows errors by optimizing your registry

I'll definitely have to check that because it goes against what worked many times for me in WSS 2.0.

In DVWP's you're right that it has to be "displayed" but then I found the "amend the code afterwards" fix and discovered that displayed didn't always mean visible ... (But that was WSS 2.0 too) (SPD for DVWPs btw - I don't know about VStudio)

Mike Walsh

"callahan" <cacallahan@xxxxxxxxxxxxxxxxxxx> wrote in message news:uin4TkcgHHA.4916@xxxxxxxxxxxxxxxxxxxxxxx
Mike, I just did a demonstration in front of a few hundred people proving the field needs to be visible when connecting two list view web parts. You may want to check on that fact again. I am coming to this from an IT pro position, which is using what WSS gives you, no additional development. And frankly, you must have the field listed in the view that the web part has in order to connect the fields.

To create a data view web part, Jackson Lee would need to use visual studio or at least use Sharepoint Designer if I am not mistaken.

-callahan
"Mike Walsh" <englantilainen@xxxxxxxxxxx> wrote in message news:eZgdSNXgHHA.3372@xxxxxxxxxxxxxxxxxxxxxxx
>"In order to connect web parts there must be a common field between the >two lists, and the two web parts must be displaying the common field."

True in essence. There's the minor point that when one of the web parts you are connecting is a Data View Web Part, the common field must be in the list of fields to be displayed but you can then edit the code to make sure it - although displayable - is not actually displayed.

You don't even with normal web parts (of lists) need to show a view of the List in which that common field is visible.

(Think of the common situation of two connected web parts of the same list; one showing the State and one showing the Towns in the State - their common field would be State but it wouldn't be visible in the second web part's View)

Mike Walsh
WSS FAQ http://www.wssfaq.com
No private e-mail please.

"callahan" <cacallahan@xxxxxxxxxxxxxxxxxxx> wrote in message news:OAlDUdWgHHA.4704@xxxxxxxxxxxxxxxxxxxxxxx
In order to connect web parts there must be a common field between the two lists, and the two web parts must be displaying the common field.

I bet with the group board workspace (which I haven't had a chance to check out) the template already has both lists premade and their web parts already are on the home page, and connected by their common fields.

To recreate that connection, all you need to do is see what that common field is, see if it works for you. Then create a custom list (or create a list from an existing template and then customize it) on your site, add the field that would be common with the calendar, add its list view web part to the home page where the calendar web part is (make sure the common field is in the view for the custom list web part), and then connect the two (calendar and custom list web parts) by the common field.

HTH,
-callahan
"shikarishambu" <shikarishambu70@xxxxxxxxxxx> wrote in message news:OgB3kVSgHHA.4872@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
Is there a way to connect the default Calendar webpart to lists? I do see an option called "Allow Connections" when I click Modify Web part. But, even when this is checked the connections option is disabled.

The Schedule and Reservations web part in the Group Board workspace template seems to have a calendar that connects to lists.

Any idea how I can connect to lists from the regular Calendar web part?

Thanks







.

Relevant Pages

  • Re: WSS 3 Calendar - Connecting to Lists
    ... and the two web parts must be displaying the common field." ... There's the minor point that when one of the web parts you are connecting is a Data View Web Part, the common field must be in the list of fields to be displayed but you can then edit the code to make sure it - although displayable - is not actually displayed. ... You don't even with normal web parts (of lists) need to show a view of the List in which that common field is visible. ... Then create a custom list on your site, add the field that would be common with the calendar, add its list view web part to the home page where the calendar web part is, and then connect the two by the common field. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: WSS 3 Calendar - Connecting to Lists
    ... the field needs to be visible when connecting two list view web parts. ... two lists, and the two web parts must be displaying the common field." ... the List in which that common field is visible. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: WSS 3 Calendar - Connecting to Lists
    ... In order to connect web parts there must be a common field between the two ... lists, and the two web parts must be displaying the common field. ... field that would be common with the calendar, add its list view web part to ... even when this is checked the connections option is disabled. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: WSS 3 Calendar - Connecting to Lists
    ... the field needs to be visible when connecting two list view web parts. ... You don't even with normal web parts (of lists) need to show a view of the ... List in which that common field is visible. ... the field that would be common with the calendar, ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Mimicking Relations with Lists
    ... > Data Access Pages and Access reports to accomplish this. ... >> lists, and create a relational looking affect with one being linked to ... >> other through a common field. ... >> options dependant on the selection of the first list? ...
    (microsoft.public.sharepoint.windowsservices)