21

Since you are using SharePoint 2013 I would recommend you to consider the following approach. In SharePoint 2013 was introduced a so called Client Rendering Mode (CSR) which is intended for rendering of List Views and Forms using HTML and JavaScript and which is a default rendering mode. About View selector menu As part of CSR ClientPivotControl control (...


6

I do not think that can be done. It shows the 4th view only once we click on it. (Dynamic HTML) But I found a workaround. Go to Edit Page. Click on Add web part and add a content editor with the links to all 4 views. Edit list view web part and disable the view selector menu. Also if needed, set tool bar to no tool bar and remove search. (Look where to ...


3

I think the friendly URL is stored in the catalog, not the page itself. You'd probably be better off using a Content Search Web Part (in most cases). It's the "new" way to do DVWP-like stuff, but it's also different tech than you are used to. You can build your own Display Template that sits underneath the CSWP to display the data.


3

With a little help from the guys over at stackoverflow I got this figured out. Putting a handler on the <a> tag that stops event propagation. What I added: groupby.find("a").click(function(e) { e.stopPropagation(); }); What it all looks like: $(document).ready(function() { var groupby = $(".ms-gb"); groupby.click(function(){ ...


3

From MSDN for SharePoint 2013. If you want complete control over how a Web Part appears on your site, and if you want that Web Part to appear on all pages of a certain type, add the Web Part directly to a page layout. If you want a Web Part to appear on all pages in a site, you can also add a Web Part directly to a master page. Try with this ...


3

One way to deal with the issue is by utilizing the content by search and filters/refiners. You can also create a result source which retrieves the indexed results from the specified list. If your columns in a list were created as a site column, it will automatically have crawled properties. You can use 'RefinableString' property and map your indexed crawled ...


2

The commonly proposed workaround for field types that don't allow to be selected as additional columns when configuring a lookup field is to add a column of type text for each property you need to show on the related list and populate it via a workflow fired on item creation/editing. If you don't edit your existing InfoPath forms, InfoPath won't complain. ...


2

In Discussion Board for storing questions (Body field in Discussion Content Types) and answers (Body field in Message Content Type) is used Enhanced Rich Text field that allows to upload files and insert file links. So, Upload file RTE command could be used to upload files into Documents library and insert links into questions and answers in ...


2

Try this <xsl:choose> <xsl:when test="@Within_x0020_Product_x003F_=1">Yes</xsl:when> <xsl:otherwise>No</xsl:otherwise> </xsl:choose>


2

DataView is not quite suitable solution to show information from two lists, because it basically makes CAML query to the list. You can implement your requirement using Search. You can use Search Query Web Part. You can look here https://support.office.microsoft.com/en-us/article/Configure-a-Content-Search-Web-Part-in-SharePoint-0dc16de1-dbe4-462b-babb-...


2

If you are looking for the best practice I would definatly recommond looking for a Javascript solution.There many tutorials available on how to do this. You could think about creating a html file, use it in a Content Editor Webpart, loading the data through rest and displaying it with a javascript chart library. One example of a chart: http://blog....


2

I would solve this problem to add new site for this type of excel sheets and use it wide layout (change masterpage) for it which will be accurate for excel sheets


2

Heavy subject! Not going to try to explain it because this gentleman excelled at it: http://www.nothingbutsharepoint.com/2011/08/11/understanding-filters-in-sharepoint-list-views-aspx/ Just 2 general tips: Remember that the conditions in operators are grouped from the beginning. Operators are taking effect between all conditions on the left of the ...


1

You can try below <td class="ms-vb"> <xsl:variable name="PropertiesURL"> <xsl:value-of select="@EncodedAbsUrl"/> <xsl:value-of select="@Path" /> <xsl:value-of select="'/Forms/DispForm.aspx?ID='"/> <xsl:value-of select="@ows_ID"/> </xsl:variable> <a href="{$...


1

You can create a filtered webpart that connects with the DataView WebPart that filters based on a search result type of your choosing (Text, URL Parameter, Choice, etc). That acts as a search for that webpart. Add the Text Filter Web Part to the Web Part Page. In the Text Filter Web Part, click the Open the tool pane link. Edit the custom Web Part ...


1

Yes it can be done, I'm currently doing it on something I'm working on. The key is to have a fixed width container for your items. Then for each item, it sits in a div with a fixed width and displayed inline-block. This will get you the automatic wrapping you want. <div style="width: 900px;"> <div style="width: 280px; padding: 10px; display: inline-...


1

Try the grouping toolbar feature that is built-in to the DVWP. Instead of "Sort & Filter on Headers" in the Design ribbon, you can use the Options drop-down in the Design ribbon and then tick "Grouping Toolbar". This will add XSLT to the DVWP that contains drop-downs for each column. You can edit the XSLT and remove the drop-downs you don't want. Using ...


1

Anish, This thread should help using (SPLimitedWebPartManager mgrPageManager = pageOrganisation.GetLimitedWebPartManager(PersonalizationScope.Shared)) { SPList organisations = oHomeWeb.GetSafeListByName(SponsoringCommon.Constants.LISTNAMES_ORGANISATIONS2); XsltListViewWebPart lvwpOrganisation = mgrPageManager.WebParts[idWebPartRootOrganisation] ...


1

The easiest way I know of to do this is to put each image in a div and then use css to float those divs left. SharePoint already has a float:left class you can tie into: "image-area-left". So your item style in xsl would look like this: <xsl:template name="dvt_1.rowview"> <div class="image-area-left"> <img class="image" src="{@...


1

Do a search for "Laura Rogers Data View Web Part" and review articles on EndUserSharePoint.com (alot of her articles are there). She covers quite a bit on how to use them and style with XSLT. You will find others that have contributed on the topic there as well. XSLT is the view engine - it's going to generated based on your data source, and so is ...


1

There are a couple of ways to migrate pages. You can package into a solution then deploy the solution in your target farm. Another way: take a backup of the complete site collection and restore the site collection in the target farm. Or you can use 3rd party tools. One is free from codeplex. You can find the details here: http://spdeploymentwizard....


1

This is a broad question and there are multiple ways to approach it. First, you need to decide where to get the "associated information". If it's just a couple fields, you could consider loading it within the data view. If it is a bigger chunk (e.g. includes images), then you'll load it on demand with an AJAX call when the user selects an item. [Edit] ...


1

I have created a similar solution that is done using Client side scriping (jQuery), it hides all the rows initially and shows them based on options selected. You may get some idea from this solution. Please have a look at jQuery - Filtering SharePoint lists


1

One option you have is to implement filtering in the client side. I have done this in one of my implementation, i used to pass the values from a page using Query string and on the list view page i had another script to read the values and display only matching rows. Check jQuery Filters


1

Your data view web part will only refresh on page load by default. Since your code runs in response to a button click, modifying the data, your data view is now displaying stale data that is no longer accurate. There are three ways you can handle this: Refresh the page. i.e. window.location = window.location;. This is easy to accomplish, and guaranteed ...


1

Regarding your first question: you can also use PowerShell to accomplish this. Powershell has built in cmdlets to open and process XML and the SharePoint cmdlets will allow you to easily insert this data into a list. This snippet shows how easy it can be: Use the [XML] type accelerator to convert results from Get-Content into an XML document, and then ...


1

Ya, unfortunately the Related Item field isn't connectable because it's a link. What I always do is create a column in the Task list that the workflow uses called RelatedId, and whenever a new task is created, have the workflow populate that column with the related content's ID. This way you can do connected web parts and filter.


1

If they are connected web parts, you should be able to do something in the XSL to set the wrapper of the visible web part to display none given some condition. Like if the resulting row count is zero give the wrapper a hidden class or use a different template. Without more context, this answer is a little vague.


1

I don't think you can do that in xslt but you can do that on client side using ecma script: <script type="text/javascript"> var siteUrl = 'Your site url'; var serverRelativeUrl = 'your page url'; function retrieveWebParts() { this.clientContext = new SP.ClientContext(siteUrl); var oFile = clientContext.get_web().getFileByServerRelativeUrl(...


1

So I assume you are saying you tried to display something during the onload and call the rest of your code right after in a later event or in onload. With ASP.net, nothing is drawn or changed in the UI until after the RENDER event. If you want to display a loading image, you must allow the postback to finish, then use javascript to draw the load image and ...


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