Tag Info

New answers tagged

0

First, create document library A and add all the docs through Windows explorer. Then create a second document library B and foreach file in A: SPListItem item = file.Item; item["Content Type"] = "Link to a Document"; SPFieldUrlValue itemUrl = new SPFieldUrlValue(); itemUrl.Description = "From sample code"; itemUrl.Url = fileLinkUrl; ...


1

I agree with PirateEric. A forms library will only be required if the features of a list form are not sufficient. If you can make do with a list form, you can save all the extra work required to promote fields to library columns and all list columns are available to Excel by default. Other advantages of a list compared to a library: you can configure ...


-1

InfoPath forms are generally stored in a Forms Library. Basically you design the form at InfoPath then create a new library using the feature that is available in InfoPath (Publish to SharePoint). All the values in the form are displayed in a list format which you can administer. When you view/edit a particular entry, that will be displayed in the form. ...


0

My general rule of thumb when using InfoPath revolves around if the form is going to hold any repeating data. If it is, then I usually opt for it to be stored in a document library. If there isn't going to be repeating data, then a list is sufficient.


0

Should this field be editable to SPGroupA and not editable to SPGroupB? You can use javascript scom to find the SP group that the current user belongs to : http://stackoverflow.com/questions/22122139/check-if-current-users-belongs-to-sp-group-using-javascript-client-side-object-m And then make the field read-only : ...


0

I have code I use to upload files using the filereader object. The uploadFile function is called on the event change of a file input and passes the event.target.files to the function. If you are using IE you will need to use a polyfill to provide the same functionality. I have used https://github.com/Jahdrien/FileReader. Event Object: jQuery('#' + ...


0

Assigning permissions at the column level is not possible. My workaround: Create a calculated column (for example "Column001_copy") and give it the formula: "=[Column001]". Display this column in the list view for your user instead of the editable column.


2

Probably the most simple option would be just to hide List View Toolbar Open the page in Edit Mode Go to XLV web part properties and specify Toolbar Type: No Toolbar That's it. P.S. Of course, you could accomplish the same task using CSS or JavaScript , but what for..


1

Edit the page and add the following CSS inside the content editor webpart: td.ms-list-addnew { display: none; }



Top 50 recent answers are included