Tag Info

Hot answers tagged

6

Have you tried if (!Page.IsPostBack) { your code here } ?


5

Cross-Page connections are only supported by a few old webparts as it became obsolete after SharePoint 2003. In order to support Cross-Page connection the web part need to: derive from the Microsoft.SharePoint.WebPartPages.WebPart instead of System.Web.UI.WebControls.WebParts.WebPart (the recommended approach since WSS2.0/MOSS2007) declare the interface ...


5

saving session state varibles can be done using: public string Name { get { return Page.Session["SaveName"] as string; } set { Page.Session["SaveName"] = value; } } this is a getter/setter to save/get from session state to use this do the following: this gets the value ...


4

I created three web parts connected together and filterable using Title: Choose a color -> Choose a fruit -> View fruit details. I created the following selector (jQuery required): $('img[alt="Selected"]').parent().next().children('div.ms-vb'); Which returns an array of the selected elements which have an ID attribute. You could then do a simple each ...


3

Not with OOTB default webparts. You can convert these to data view webparts and utilize multiple connections.


2

If you think that it is hard from an end user's standpoint, try doing development with it! I think they have simplified it some over the 2003 version. The one thing that you have to keep in mind is that the data being passed must be defined. There are different "formats" for this contract; Row, Cell, or Parameters. The provider and the consumer must be ...


2

Hmmm...did a little quick digging, found some interesting resources: A nice write up of the mechanics of how they work. Not completely end user, but not exactly dev-oriented either - MSDN Web Part Connection Overview A hands on walk through of setting up a connection from the SharePoint Designer Team blog - Creating Master-Detail views with Web Part ...


2

The major difference in these approaches is that in the second approach the interfaces listed here http://msdn.microsoft.com/en-us/library/ms469765%28office.14%29.aspx are specific to SharePoint so these would only work when you are developing SharePoint web parts but the first example is generic and is SharePoint independent. In scenarios where you just ...


2

To accomplish that, you'd need to have some code that dynamically sends a query string prameter over to the newform page of the Notes list. The newform page would have some code on it that parses the query string and sets the desired drop down list value depending on who the user is. Typically those associations have to be built, SharePoint doesn't do ...


2

If the Web Part that is being connected to is on another page, connectedPart is null. You can use IWebPartParameters Interface and it is clearly mentioned on IFilterProvider Interface [ObsoleteAttribute("Use System.Web.UI.WebControls.WebParts.IWebPartParameters instead")] public interface IFilterProvider Here is a sample which using ...


2

Same happened to me when I tried to send two connections from one provider to one consumer... I tried this, but I obtained the same error: A -> B A -> B To solve this I created a third WebPart between A and B. In my context it had sense, since the new WebPart had a different use than A. So my result was: A -> B A -> C -> B I hope this can help you.


2

This error simply means that the web part being edited does not support connections - it has not been coded correctly. In this case I was receiving the error because I placed the ConnectionProvider and ConnectionConsumer attributes and methods on the UserControl objects inside the Web Parts, rather than the Web Parts themselves.


2

As it seems this is a limitation of the managed metadata columns in SharePoint 2010. Let's hope a future SharePoint version will improve this behaviour.


2

This is how I got it to work. Create a small serializable class in my provider which implements the interface the consumer saves its' reference to the class in its' ViewState on PageLoad the consumer is able to communicate with the provider using the instance of the class staored in the ViewState WARNING the consumer should first read the value from the ...


1

Have you ruled out all the solutions we suggested on your other post? http://www.sharepointoverflow.com/questions/6753/cant-access-sharepoint-site-from-local-workstation/6754#6754


1

I think the real reason is that the team that developed these controls initially didn't know how to use web part connections. But it gives the following advantages (which MS probably will claim is the reason). Easy setup on single query page On most search pages users only have a single query. The current implementation makes it easy to add new search web ...


1

If you want two webparts to talk to each other than you would need to make an Interface class. The interface class connects the consumer and provider class through inheritance. Its quite easy but if you want to have an ajax updatepanel to performe a partial postback then that is a different ballgame its quite hard to figure out as its a hit or miss with ...


1

You can connect two webparts by following link V-B mentioned in comment, however you can also use Ajax Update Panel in one webpart to get your work done but it depends on what your trying to do. e.g. having 2 update panels selecting something in one panel will produce results in 2nd panel without any postback. ...


1

What interface are you using? (HINT: post your code ;-) Standard lists support IWebPartField, IWebPartRow, IWebPartTable and IWebPartParameters. Which you want to use depends on what you want to achieve. Often you would like to transfer the whole row of data, so you would use IWebPartRow. ...


1

I would try useing jQuery/COM to get URLs from list dynamically and hardcode this inside CEWP


1

Create two parameters in the class and add another method, like such: string test1; string test2; [ConnectionProvider("People Picker Filter1", "ITransformableFilterValues", AllowsMultipleConnections = true)] public ITransformableFilterValues SetConnectionInterface() { return test1; } [ConnectionProvider("People Picker Filter2", ...


1

i able to fix with the help of this link http://www.sharemuch.com/2010/03/19/resolving-vs-2010-solution-deployment-issues-for-sharepoint-2010-projects/


1

Have you checked the project build properties to ensure that it's targeting "All CPUs" as opposed to x86? I recall this throwing me off in the past.


1

Tried IWebPartRow? http://msdn.microsoft.com/en-us/library/system.web.ui.webcontrols.webparts.iwebpartrow.aspx


1

If this is like what I ran into it 'happens' because of the Page cycle - in other words the WebPart that is supplying the value has to exist before it can supply that value to the WebPart that is consuming it. As a result you have to handle the data results in the PreRender override. I may have misunderstood, however, the problem you were having....


1

His webparts need to be within a single updatepanel (With this properties). Consider the following code: <asp:UpdatePanel ID="updData" runat="server" EnableViewState="true" ChildrenAsTriggers="true" UpdateMode="Always"> <ContentTemplate> <WebPartPages:SPProxyWebPartManager runat="server" id="spproxywebpartmanager"> ...


1

I'm not familiar with this area of Sharepoint, but after looking through those links, it appears that they are actually closely related. Here's my take on it: The simpler tutorial shows you how to create linked web parts by using a simple interface you define in your own code - IProject - which has nothing but an ID and a name The advanced tutorial shows ...


1

Unfortunatley the Slideshow Web Part does not have any consumer connections. You need to build a custom slideshow Web Part to be able to connect it to another WP.



Only top voted, non community-wiki answers of a minimum length are eligible