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.


3

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/ Steps from the Site Check what user vssphost14.exe (or vssphost15.exe) is running as (Generally the same user you are using to run VS) Launch SQL Management Studio and connect to your SharePoint SQl ...


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


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

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


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


1

If you want to avoid a reset you will need to find some way to create a custom solution with ajax that is able to interact with the server without doing a post-back.


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.


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

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

Tom, Laura Rogers has done a lot of work with connecting web parts. I don't think she has much info on her blog, but she may be able to give you some assistance if you ping her. @wonderlaura on twitter.


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

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

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


1

I've found exactly what I was after here. I followed the tutorial and everything works great. http://geekswithblogs.net/SoYouKnow/archive/2010/12/16/creating-a-sharepoint-parentchild-list-relationshipndash-sharepoint-2010-edition.aspx


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.



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