Hot answers tagged

8

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 ...


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 ...


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

If you want to manually navigate to the doc set, here's the correct URL: ...


3

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


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

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 ...


2

The major difference in these approaches is that in the second approach the interfaces listed here 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 need to supply couple of values, you should go with the first example, ...


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

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

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 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

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/


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

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 ...


1

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


1

Adding DBO permissions to the sharepoint databases has resolved the issue


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

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 needed to implement the ITransformableFilterValues interface.


1

Someone on the Microsoft forum suggested the following workaround which does its job well: Add a hidden text column to both lists. Use a workflow which is triggered on item creation and update to copy the value of the hyperlink column to the hidden text column. Connect both webparts using the hidden column as filter. Nonetheless, I still wonder whether ...


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

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

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

I would need to see your code to know whats going on, but looking form the example can you change: public void GetTableData(TableCallback callback) { callback(_table.Rows); } to public void GetTableData(TableCallback callback) { callback(_table); } the issue is in the provider class that is sending the data to the consumer class. The I think ...


1

The error in my case lays in using the CreateChildControls and the OnPreRender functions. I called the provider in the CreateChildControls while it should have been called in the OnPreRender function. If you call a different Webpart in the CreateChildControls it is possible that the CreateChildControls of that webpart have not been initiated. When ...


1

I think the V2 APIs where in the SharePoint namespace and the connections in the WSS V3 web parts are part of the ASP.NET Namespace. My guess it that is why they are not compatible. I know you can still create a web part using the SharePoint namespace with V3 (not recommended by MS unless you need to). It's possible the web part implementation for consumer ...


1

How did you get the v2 web parts to work in v3? With the .net framework difference I'm not sure how this is possible unless you have the source. I had developed a couple of applications for SPS 2003/WSS 2 that utilized the original web part connection methods that were deprecated. I wasn't able to find a way to easily upgrade or recompile them for ...



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