17

I can't really provide a sensible answer to why this is happening (I can confirm I'm experiencing the same weird behavior. I'm sure this is related to the fact that they cut out the designer part without properly thinking about the consequences this would have had). What I can offer is a dirty workaround that proved to be almost always working in my case. ...


10

Use the following URL to get XML of list:- http://{0}/_vti_bin/owssvr.dll?Cmd=Display&List={1}&XMLDATA=TRUE {0} – The URL to your site. This could be the root web or a child site. {1} – The GUID for your list. To find the GUID for a list, just go to the Settings page for the list and copy it from the URL. Use the following URL to get XML of ...


9

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


5

The rendering of column headers could be customized using XSLT. The method described here represents one of the possible ways how it could be accomplished using SharePoint Designer (SPD) Solution In SharePoint Designer (SPD) open view page in Designer Mode. Select list header in List View that have to be customized and then click Customize Item as ...


5

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


5

You're missing the WebId property: var xlv = new XsltListViewWebPart(); using (var oSite = new SPSite(" http : / / app:3333/ ")) { using (var oWeb = oSite.OpenWeb("/ProxymIT/Direction")) { var oList = oWeb.Lists["AdministrativeNotes"]; //your list name xlv.WebId = oWeb.ID; xlv.ListId = oList.ID; xlv.ViewGuid = oList....


5

You can't. The ListViewWebPart does loading and paging on the server-side. If you now remove the rows using JSLink they'll be simply "hidden" (kind of) on the client side. The ListViewWebPart knows nothing of what you did and "thinks" the rows were all rendered.


4

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


4

I have created this in an application page, which is working fine. Please refer tto the code below that also has your part of code. using (SPSite site = new SPSite(SPContext.Current.Web.Url.ToString())) { using (SPWeb web = site.OpenWeb()) { SPList list = web.Lists[MyList]; ...


4

You can create your own view and decide which fields to show in the view. The method below creates a StringCollection which can be passed to the method while creating view List.Views.Add() private StringCollection CreateViewColumns() { StringCollection viewFieldsCollection = new StringCollection(); string tasksColumns = "ID;Title"; ...


4

Uninstall windows update KB2844286. Over the weekend I had to do this to two servers (much to my annoyance) but it did fix this problem. A server reboot was required. http://social.technet.microsoft.com/Forums/sharepoint/en-US/cc9a557b-93cd-40d5-965c-e0a2f107624d/unable-to-display-this-web-part-error-message-after-patch-kb2844286


4

I found the way to make it work: overrideCtx.Templates.Group = CustomGroup; function CustomGroup(ctx, group, groupId, listItem, listSchema, level, expand) { var html = '<div style="float:left">' + listItem[group] + ' : </div>'; return html; }


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


4

This might classify as more of a work-around than a solution, but I used the guid of the view as the webpart id. I decided to look into the content database to see how views are stored. In the stored procedure proc_CreateView I found that views are actually stored in the AllWebParts table with the ViewId inserted into the tp_ID column. So I added the ...


3

I believe it is related with invoking template for a field, it means that in your case this template is not invoked at all. In order to render field using your template the following attributes should be specified in template: a) mode DateTime_body b) match(matches field by internal name in that case) <xsl:template name="FieldRef_DateTime_body....


3

Filters cannot be associated with a calendar view. Since the calendar view of a list will not support web part connections.


3

This is an issue with InplView not loading on demand when a publishing page is in published state. Still a bug in Feb 2017. To force the script to load, add the following script to the page: window.vendor_ensureInplView = function () { var typ; if (ajaxNavigate.get_hash().indexOf('InplviewHash') === -1) { try { typ = typeof ...


3

Firstly you need to be cautious adding a LVWP to a page layout as it could potentially be used on a different site to the location of the list. If this is the case then you should use a CQWP or in 2013 a Search web part which will not cause any issues across sites. I do not have much experience with 2013 yet but with 2010 I can add web parts directly to ...


3

I solved this problem by using page view webpart on the document library with "?IsDlg=1" added to the url arguments: /File Archive/Forms/AllItems.aspx?IsDlg=1


3

Why not just switch ON the Dialogs option for your list? This option can be found here: List settings => Advanced settings => Dialogs => switch to "Yes" Yes, I know, I know, external lists don't seem have "Advanced settings". But you still can get there! Do the following: Go to your external list settings page From the address bar, copy out the List ...


3

To get a WebPart you use the Limited Web Part Manager The SPWebPartManager manages all the Web Part controls, functionality, and events that occur on a webpage.. For example using (SPLimitedWebPartManager wpm = web.GetLimitedWebPartManager(this.Page.Request.Url.AbsolutePath, PersonalizationScope.Shared)) { foreach (System.Web.UI.WebControls....


3

I am displaying a tooltip with the title of the item, using the below code. $(document).ready(function() { ExecuteOrDelayUntilScriptLoaded(tooltipDisplay, "sp.js"); }); var itemID = ""; var title = ""; var offset = null; function tooltipDisplay() { $("table.ms-listviewtable tr.ms-itmhover").hover(function(e){ var iids = $(this).attr(...


3

As Waqas Sarwar MCSE mentions, this is very easy to do programmatically. You need someone with the following skills: HTML, CSS, XML/JSON, Javascript. Create a script webpart on the SharePoint page and give your developer the following piece of code: _spBodyOnLoadFunctionNames.push("myCustomFunctionName"); function myCustomFunctionName() { jQuery.ajax({...


3

You could export the content query web part and open it in notepad. Then define the MainXslLink and ItemXslLink property values as "/rootsite/subsite/style library/xsl style sheets/Xslfile name.xsl" in the content query web part. And you also could change the url of the xsl file. Make sure there is a major version of the published xsl. There is a similar ...


3

If MDS is enabled, you may need to take extra steps to ensure that your CSR script is recognized by the MDS system as something that needs to always run. The MDS system has a function called RegisterModuleInit that has two parameters - a path to a script file, and the name of a function in that file that should always be run. So in order to get the CSR ...


3

You can hide the search box by editing the webpart properties. Edit webpart--> Uncheck "Display Search box" (Under Miscellaneous) If you are provisioning the webparts using modules into a page, you can edit the webpart xml and change property InplaceSearchEnabled from True to False like below: <property name="InplaceSearchEnabled" type="bool">...


2

In your case for rendering Taxonomy field in template the following attributes are specified correctly: a) match attribute (value correspond to field internal name) match="FieldRef[(@Encoded) and @Name='Country']" b)mode attribute (Taxonomy field has Lookup type) mode="Lookup_body" Please remove another attributes, your template should look like shown ...


2

Yes this is sharepoint OOTB error.. No solution for this If you want all users to have search enabled you can break permission and give them contribute permision at list level. Enable the show ribbon ->Always true


2

Explicit attribute will hide the column in the webpart <FieldRef Name="LinkFilename" Explicit="TRUE"/>


2

The problem is that $thisNode/@Created is represented in french format (10/02/2013 for Feb 10th, 2013), but the FormatDateTime() function expects it to be the other way round (i.e. understands October 2nd). This is in particular annoying, because it tries to tolerate "obvious errors" like 31/12/2013, which becomes correctly Dec 31st (which ShPt beleives is ...


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