Tag Info

Hot answers tagged

4

I suggest you check out SPServices. It's a "jQuery library which abstracts SharePoint's Web Services and makes them easier to use." http://spservices.codeplex.com/


4

Don't know really HOW, but this code works! Take a look =) public partial class VisualWebPart1UserControl : UserControl { private Microsoft.SharePoint.WebPartPages.ListViewWebPart myListView; protected override void CreateChildControls() { base.CreateChildControls(); SPSite oSiteCollection = SPContext.Current.Site; ...


4

In brief, just don't use XsltListWebPart on Application Pages. And here are some summarized explanations: XsltListViewWebPart and other OOTB SharePoint webparts (especially complex ones), apparently just aren't supposed to work in Application Pages environment. In other words, they weren't tested there and thus their operability is not guaranteed. This ...


3

Thanks Robert! I am banging my head on the wall for this! Basically you don't have to add a code just to show the ribbon by default. Just go navigation and tick NO to show or hide command ribbons. According to the error that i got below, it is referencing to a script outside our domain. Webpage error details Message: Script error Line: 0 Char: 0 Code: ...


3

You can do this by editing xslt in spd, namely you should change <xsl:value-of select> tag and add the surrounding <a> <a href="http://vxmc2170345/Lists/facilty/DispForm.aspx?ID={substring-after($thisNode/@IDofListX., '#')}"> <xsl:value-of select="substring-after($thisNode/@IDofListX. , '#')"/> </a> more detail: ...


3

Just manage to find the answer as follows: Select the list view web part and modify it and remove the 'Title URL' under the 'Advanced' section will do. Reference: http://intl.feedfury.com/content/16270498-how-to-remove-the-web-part-title-bar-link.html


3

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


3

The only out-of-box WebPart that supports audience filtering by content item is the Content Query Web Part. It is part of the Publishing Infrastructure Site Collection feature and requires SharePoint Server edition (not included with Foundation). Add a CQWP to your page, wire it up to your linked list, and then click the checkbox to enable Audience ...


3

I tested your code and I can confirm the behavior you described. There seems to be a bug where, no matter what XmlDefinition you specify, a webpart attached to a document library always ends up showing the default OOB view (Name, Modified, Modified By). If it were server object model, then it would be possible to cast the webpart to the underlying object ...


3

I came across this today and found another workaround. When the web part is added to the page it creates a hidden view on the list it is bound to. You can get the hidden view and make the changes to it directly. This works for announcements, calendars and doc libraries from what I have tested so far. Example: private static void AddWebPart(Web web, ...


2

Ok I resorted to a jQuery solution as I can get my head around it easier than anything SharePoint throws at me! As all lists have the class ms-summarycustombody I was able to get the following to convert the table to ul var div = $("<div id='viewport' class='viewport'></div>"); var list = $("<ul id='announcementList'></ul>"); var ...


2

myListView.ViewGuid = list.DefaultView.ID.ToString("B").ToUpperInvariant(); did the trick for you... If you set the ViewGuid property, it needs the Guid of the particular View Case sensitive!


2

Since XsltListWebPart.ViewGuid and XsltListWebPart.XmlDefinition properties are ignored when adding web part via CSOM it makes it impossible to specify custom view for XsltListWebPart web part. Solution Since the default view is used when web part provisioned via CSOM, the proposed solution would be to modify default view during web part provisioning: ...


1

This is the 2007 way to do it, but something like this. You can load the web part or web control inside of the 2010 web part and place it in a container which is styled. Here


1

First, I think Andrey hit the nail on the head. In addition, you could try to use the ListViewByQuery control on an application page if you are looking for a simple tabular layout of data (i.e. a list). Microsoft does this in the OOB workflow status page (i.e. _layouts/wrkstat.aspx) for display of tasks. I've not tried it with ECB menus and such, but ...


1

Finally I found the answer for this problem. I need to use XsltListViewWebPart instead of ListViewWebPart for the List View Web part in elements.xml


1

At site collection level, create a site lookup column(Say, TestColumnX) that refers to your list Say "TestListA" and point to the title field. On your child site, go to you desired list settings and add a new column based from an existing one. Pick the one you just created.


1

I've seen this problem before, on a Document Set homepage. The problem is that each webpart renders its own context object in DOM of the page, to be used in various javascript functions like sorting, paging, and also setting the ribbon. Despite extensive investigation the best answer I can give you is that you need to decide which of the webparts is most ...


1

so, I resolved it with my colleague help, on create child controls I do following. Take schema xml from the view, overwrite query and pass it to list view. No new view is created and everything works. var obtainedList = elevatedWeb.GetListFromWebPartPageUrl(FullUrl); if (obtainedList == null) { throw new ...


1

Tom, For cross-site queries you can use SiteDataQuery Then you can use SPGridView to show results, here are some samples on using SPGridView... OOB AFAIK is not available what you trying to achieve, but when it comes to code - you CAN!


1

If you know the title of your list you could try something like this (here from Feature Event Receiver): var web = properties.Feature.Parent as SPWeb; if (web == null) return; var list = web.Lists["MyList"]; var manager = web.GetLimitedWebPartManager("MyPage.aspx", PersonalizationScope.Shared); var xsltListViewWebPart = new XsltListViewWebPart { ListId = ...


1

fallout, I had the same problem and it was solved simply by using XsltListViewWebPart class instead ListViewWebPart. Hope that it helps,


1

you can find the ListViewWebPart by code and set the HtmlSchemaView property by reflect. here is a open-source project : http://camlquery.codeplex.com/ you can find how to set the query condition of ListViewWebPart dynamically.


1

Edit the webpart file to set the default value using the property tag <property name="" type="">[value]</property> It probably isn't working because once it is altered you can't set the default property again in that webpart.


1

it sounds like you are using all oob webparts. In this situation - if I'm understanding it correctly - I would use jQuery to handle your presentation. If it's custom webparts then I would handling completely different (all in the webpart itself). So, I think your on the right track by using jQuery if I'm understanding the situation correctly.


1

You can add several list filters through sharepoint designer but you cant do this through the front end web page


1

I think you are using webpart connections. If so, You cannot do this. A webpart can only be connected to another webpart through one connection type and Each connection can have only one connection type. So, you cannot establish two connections between same instance of Provider and Consumer webpart. However, You can connect a provider web part with two ...


1

Maybe this link from stack overflow site can help you to create multiple filter webpart OR You can passing two or more filter parameter by using query string web part. This link will give you tutorial how to use query string webpart to filter list item. You can use custom control to add query string to your site url. Hope it solve your problem.


1

For the list view form, deleting and recreating the views worked for me: private static void RebuildView(SPList list, SPView view) { list.Views.Delete(view.ID); list.Update(); string title = view.Title; SPView cloneView = view.Clone( title.Replace(" ", string.Empty), view.RowLimit, view.Paged, ...


1

I find this article from MS http://support.microsoft.com/kb/2639184



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