Hot answers tagged

6

You need to use one of the following: Content Search Web Part Search Web Part Content Query Web Part The two search web parts are a bit easier to use as far as customizing the queries as there is a designer you can use. You can also change their looks. Content Query Web Part requires some XSLT knowledge to get the most out of it. You will add the ...


6

There can be many advantages if you target your users to the Web Part Page on which you have a view of a List. And they are as follows. The independent Web Part Page can be branded and have a more appealing look Instead of showing all of the items, Views are very useful in listing the filtered data. Which makes sense when you want your users to see only ...


5

By inspecting the source code i noticed the profile pic is set like this: background-image:url(/_layouts/15/userphoto.aspx?size=L&username=usernamehere);​ So I used the same url in my promoted links list and when ever a user change his profile picture the url is returning the right pic too. Because of the cache files the changed pic can't be seen ...


5

To brief it is actually a good practice to refer on a different page with list view web part added onto it. Reason is you can configure the new page such that user will not be able to use ribbon options (if want to restrict from navigating through list settings) Step to hide ribbon: Edit your webpart Select Toolbar Type to None Chrome Type to Border Only ...


5

Exporting and importing as html will not work in SharePoint as it refers lots of controls and files internally Thee best suggested option would be to open the page in designer and copy the content to target page** but make sure all the those web parts are already in the web part gallery and fully functional. To check all webparts are in the gallery,...


5

After banging my head around for some days, the problem was solved by flushing the blob cache. This is the command I used on the Front end server $webApp = Get-SPWebApplication "<WebApplicationURL>" [Microsoft.SharePoint.Publishing.PublishingCache]::FlushBlobCache($webApp) Write-Host "Flushed the BLOB cache for:" $webApp https://technet.microsoft....


4

Try adding the query string parameter to the URL: IsDlg=1 Can't test right now but that works for dialogs. Maybe it works for the page viewer too. I can try it out when I get back to my desk. EDIT Thanks to Akhoy for pointing out an issue with IsDlg when using the PageViewer web part. David Lozzi's blog describes the issue but basically, use IsDlg if ...


4

Yes, you can add webparts using the client side object model. Summary: Use the LimitedWebPartManager defined for C# or JavaScript. Adding webparts is generally considered part of a provisioning solution and the OfficeDev Patterns and Practices (PnP) repository on GitHub has many examples that demonstrate different provisioning techniques. One specific ...


4

Trick is to attach a JavaScript keyup event to the existing Searchbox for every ListItem (in this case above the Searchbox in the DOM, because events bubble up anyway) Each script can check against any content you can reference in a Calculated Column... that means no enumerables like Person fields or Multiple Select Choices. If you stuff it all in a ...


4

No. A list is always presented in the same way, using the same web part either if you go to the original list location or add it somewhere else. The only difference there is for your web part page is that the list web part toolbar type has been set to No Toolbar. If you choose to edit the page and then edit the list web part, you can change the setting ...


4

In the Web Part properties Change current view Uncheck the column title linked to item or title linked to edit menu Select title, it would just say title No need for SPD or any customization.


4

A web part page with a list web part on it is actually exactly the same as "the list itself". When you say "the list itself", THAT is a web part page with a list view web part on it. Nothing more. So if you want to direct your users to a list called "My List", you can direct them to the default AllItems.aspx page for the list, or you can direct them to a ...


4

One way is to put the page in to "maintenance" mode by simply adding "contents=1" in the query string. So for example: http://sharepoint.yours.com/site/pages/page.aspx?contents=1 Then, you will see the types of web parts on the page.


4

Address the web parts by giving them a common class and then use the following: document.getElementsByClassName Instead of document.getElementById


4

try opening the page and adding ?contents=1 to the end of the URL to get to the WebPart maintenance page. There you can see existing WebParts. Try referencing this solution


4

You have to provide js file URL in JSLink property each time while adding your list view web part on the page. List and the list view web part are not the same thing. Saving the list as a template will give you the functionality of generating the same list with same columns and also with including data but will not include list view web part. List view web ...


3

Best way to move SharePoint solutions is using .wsp file which is created as you deploy any solution just copy from development, paste in production and then add and deploy solution there by power shell. To move list use export functionality in central admin of development and then import the .cmp file in production. done!


3

We could do that by applying this method: 1- Create Subsite and Enable “Site Feed” feature. 2- Add “Site Feed” WebPart in the new Subsite 3- Go to Main Site and do the same “Enable Site Feed Feature” and “Add Site Feed to home Page”. 4- In the main Site, add “Page Viewer” webpart and put as a link the page created before which contains Subsite Feed”. 5- ...


3

Try adding the type="text/javascript" in the <script> tag references, like this: <script type="text/javascript" src="http://yoursite/sites/yourlibrary/jquery.min.js"></script> <script type="text/javascript" src="http://yoursite/sites/yourlibrary/StickyHeaders_v2.9BETA.js"></script> Also see these posts: sharepoint 2013 / ...


3

I would create a new view in the library, sorted by modified date descending, with an item limit of 1. This will get you the most recent file in your view that you can use in the web part on the home page.


3

To avoid this issue need to specify field GUID and type when setting CommonViewFields. For example: CommonViewFields may be "{52cd2f97-2c0c-40ec-9157-143834056e4e},Description,Note;"


3

If by custom .aspx page you mean Application page than obvious difference is that application page will have URL like http://sharepointsite/_layouts/YourSolution/ApplicationPage.aspx. And these application pages are shared between different Web Applications (not specific to a Web Application). On the other side you can built reusable Web Parts and use it ...


3

When you use QueryOverride, you can no longer modify all query related values using a browser. So you will need to fix the query, reupload the webpart, and repeat those two until you have a working web part. Use the internal Field name, yours look like the display name which won't work. For Content Type filtering, best is to use ContentTypeId. <...


3

Try to delete item operation explicitly then it will work string itemId; protected void grdcrud_RowDeleting(object sender, System.Web.UI.WebControls.GridViewDeleteEventArgs e) { try { itemId = grdcrud.DataKeys[e.RowIndex].Value.ToString(); SPSecurity.RunWithElevatedPrivileges(delegate() { ...


3

Short answer: no, not out-of-the box. Site collections (what you call "parent sites") are partionned containers, and can hardly communicate data accros. With dev (creating some kind of Web part), we could achieve what you describe, but that would really be against the SharePoint "phylosophy"... However, here's a simple "hack" you can easily do: ...


3

You can preview list item metadata on hover of list item. Like: Reference Links are Link1 Link2 Link3


3

I found a solution. Here it is: I modified the view of my documents Library to display all elements flat, without folders. Then I created this JSLink: var DocuView = DocuView || {}; DocuView.itemHtml = function (ctx) { var title = ctx.CurrentItem.Title; var fileRef = ctx.CurrentItem.FileRef; var fileLeafRef = ctx.CurrentItem.FileLeafRef; ...


3

You can use jQuery's starts-with selector: jQuery( "[attribute^='value']" ) i.e. to hide / unhide webparts: jQuery( "[id^='WebPartWPQ']" ).each(function() { jQuery(this).toggle(); }); https://api.jquery.com/attribute-starts-with-selector/


3

Tnx, I had some fun with your question, applying an OOP approach Paste as snippet in Chrome Controls: function DIVManager( selector , numbers){ var manager=this; function DIV(element){ var div=this; div.state=element.style.display!=='none'; div.style=function(key,value){ element.style[key]=value; div....


3

Plenty alternative solutions explained here: http://sharepoint.stackexchange.com/search?tab=newest&q=user%3a32871%20icc Basic concept is to make the row color itself, instead of using bloated jQuery and ductaping caode on the page after it already loaded. =IF( AND ( [TextField]="text2" , [ChoiceField] = "choice1" ) ,"<IMG src="blank.gif" ...



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