Hot answers tagged

2

Actually, there's no such thing as "deploying a Web part to a site collection". You deploy a Web part with a WSP package; WSP packages (at least ones that contain Web parts) are deployed against specific Web applications. After that the feature containing the Web part is activated per site collection, but "activating a feature" is only a SharePoint logic ...


2

It sounds like the Content Type is wrong, is it associated with video content type? If so, it should direct you to the video player page and you can play your video from there.


2

Default SharePoint video player in Asset library supports only several video formats but not all. For example, clicking a .flv file in an Asset library results in opening the display form instead of the player. To distinguish between supported or unsupported videos, you can check the video icon in the default SP view in asset libraries. This is how a ...


2

Document sets are just "fanzy" folders, so you have to use scope RecursiveAll. query.ViewXml = "<View Scope=\"RecursiveAll\" /> "; Or simply use the CreateAllItemsQuery that sets the same caml markup: CamlQuery query = CamlQuery.CreateAllItemsQuery();


2

You can use content query webpart ,where you can display list from the sub-site an add the columns as per the requirement. This might help you..!


1

You can keep a Content Query WebPart on the parent site page to display the items from your subsite. Please have look to this post


1

It is not possible to have cascading dropdowns (behavior that you are describing) in OOTB SharePoint forms. There are third party solutions (both farm solution and add-ons) that add this functionality to lists. You can also have a look at SPServices jquery library and add this functionality yourself to the form. This does require some javascript development ...


1

You first need to make a POST request to http://<DomainName>/home/_api/contextinfo to get a request digest. Then you'll have to add that as a header X-RequestDigest to your actual POST to add the list item. The token is valid for 30 minutes, I believe, so you may want to cache it if you are expecting this procedure to be accessed multiple times within ...


1

Try below approach. It worked fine for me. var siteUrl = "http://mysite"; $.ajax({ url: siteUrl + "/_api/SP.UserProfiles.PeopleManager/GetMyProperties", method: "GET", headers: { "Accept": "application/json; odata=verbose" }, success: function (data) { for (var i = 0; i < ...


1

It is a usual behavior of SharePoint... When you deploy SharePoint package , it will place the files & it's related DLLs to their appropriate location.. It is necessary to reset is to connect those file with each other to get a reference from different locations ... This is the simple definition from my end to understand why it's necessary to reset the ...


1

Document Centre is the main site repository where you would start authoring (think about it as a kindergaten or school) you create, collaborate, update etc. (lots of reads and writes) Now Records Centre is your graveyard, you send the document there, there will be no more updates on it (so possibly more reads than writes, but experience shows me that there ...


1

There have to be commas between the value pairs: [ ["EmployeeNumber", $("#tbEmployeeID").val()], ["EmployeeName", $("#tbEmployeeName").val()], ["EmployeeEmail",$("#tbEmployeeEmail").val()] ]


1

public override void ItemAdded(SPItemEventProperties properties) { base.ItemAdded(properties); string title = properties.List.Title; if (title == "List Name") { SPListItem item = properties.ListItem; try { SPSecurity.RunWithElevatedPrivileges(delegate() { using (SPSite site = new ...


1

If you have kept the WebPart on the page to show the List data then by default the list title is displayed which is clickable link and it always redirect us to the complete list view. If that title is missing in your case as I guessed then you can follow this steps: Edit the page Edit the WebPart Find Appearance section and locate Chrome Type Select Title ...


1

While I haven't tested it specifically, I believe it was the Jan or Feb 2016 CU will (attempt) to parse the group claim from ADFS into AD groups within SharePoint. That said, what claim are you passing within ADFS? I usually use Token Groups - Unqualified Names to the Role claim. From within the LDAPCP configuration, you'll need to remove the prefix for the ...



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