Move documents along with versioning

Keep in mind that below approach works only within the site collection level.  I mean to say here is it is not possible to move the documents between libraries across site collection levels.

The best approach to move the documents between the libraries along with versioning is using “site content structure” option. 

Note: But one thing we should keep in mind that versioning shoould be enabled in both the source and destination document libraries.

Steps to move the documents between document libraries:

Step1: Go to Site Actions -> Site Settings.  Under “Site Administration” click “Content and structure”

Step2: Find the source library and select the all or any specific documents you want to move and then click “Actions”à Move.

That’s it. Now, go and visit the destination document library. You will get the moved documents along with its versioning’s.

One thing I observed here is, along with the documents versioning, metadata also would came.

I have a created a source document library and created 3 custom columns with different types. Uploaded the new document along with the metadata and then moved this document to destination library.

In addition to the versioning in destination library  what ever the columns available in source got created the same in destination( means 3 custom columns which are all created by me on source library are also available in destination library).

Source library:

Destination library:

Happy Sharepoint.

Please take a momenet and do comments if this post really helps

Get sharepoint Host Web Url using REST

Just do copy paste the below code and execute it.


Note: The below shared code is 100% verified/executed.

Appmanifest.xml:

Set read level permisisons to the web

Default.aspx:

The host web title is: <label id="HostwebTitle"></label>

app.js:

var hostweburl;
var appweburl;

// Load the required SharePoint libraries
$(document).ready(function () {
    appweburl = window.location.protocol + "//" + window.location.host + _spPageContextInfo.webServerRelativeUrl;
    hostweburl = _spPageContextInfo.siteAbsoluteUrl;

    // resources are in URLs in the form:
    // web_url/_layouts/15/resource
    var scriptbase = hostweburl + "/_layouts/15/";

    // Load the js file and continue to the
    //   success event handler
    //$.getScript(scriptbase + "SP.RequestExecutor.js", execCrossDomainRequest);
    $.getScript(scriptbase + "SP.js", execCrossDomainRequest);
});

// Function to prepare and issue the request to get
//  SharePoint data
function execCrossDomainRequest() {
    var executor;

    // Initialize the RequestExecutor with the app web URL.
    executor = new SP.RequestExecutor(appweburl);

    // Issue the call against the host web.
    // To get the title using REST we can hit the endpoint:
    //      app_web_url/_api/SP.AppContextSite(@target)/web/title?@target='siteUrl'
    // The response formats the data in the JSON format.
    // The functions successHandler and errorHandler attend the
    //      success and error events respectively.
    executor.executeAsync(
        {
            url:
                appweburl +
                "/_api/SP.AppContextSite(@target)/web/title?@target='" +
                hostweburl + "'",
            method: "GET",
            headers: { "Accept": "application/json; odata=verbose" },
            success: successHandler,
            error: errorHandler
        }
    );
}

// Function to handle the success event.
// Prints the host web's title to the page.
function successHandler(data) {
    var jsonObject = JSON.parse(data.body);


    document.getElementById("HostwebTitle").innerHTML =
        "<b>" + jsonObject.d.Title + "</b>";
}

// Function to handle the error event.
// Prints the error message to the page.
function errorHandler(data, errorCode, errorMessage) {
    document.getElementById("HostwebTitle").innerText =
        "Could not complete cross-domain call: " + errorMessage;
}

// Function to retrieve a query string value.
// For production purposes you may want to use
//  a library to handle the query string.
function getQueryStringParameter(paramToRetrieve) {
    var params =
        document.URL.split("?")[1].split("&");
    var strParams = "";
    for (var i = 0; i < params.length; i = i + 1) {
        var singleParam = params[i].split("=");
        if (singleParam[0] == paramToRetrieve)
            return singleParam[1];
    }
}

Thanks for visting.. Happy Sharepoint

Please take a moment and do comments on it if its really helped you.

How managed metadata works in CQWP

Please read the below good articles before go with querying the managed metadata column values through Content Query Web part:

https://chrisjohnson.tech/2014/03/25/sharepoint-querying-on-multiple-select-managed-metadata-columns-in-content-query-web-parts/

-Thanks to Chris.

https://blogs.msdn.microsoft.com/ecm/2010/05/14/whats-new-with-the-content-query-web-part/ 

Lists and Libraries: Class Day3

In this article, We will cover below mentioned topics on SharePoint Lists and libraries. please feel free to reach me if have any clarifications or more information required on it.

Topics:

1) List and Library

2) site columns and List columns

3) site content type and list content type

4) Views

4) Cascade Delete

5) Restrict Delete

6) Enforce uniqueness

7) Calculated columns

8) lookup columns

9) Permissions

10) List Threshold

11) Indexing

12) Versioning, Checked-In/Out and Publish

13) Update Vs SystemUpdate Vs UpdateOverWriteversion

14) SharePoint real-time scenarios

15) SharePoint interview questions and answers

16) Read-Only columns(Eg: Created/Created By, Modified/Modified By etc..).\

17) File URL length restriction.

18) SPBuiltInFieldId

Basics on the List and Libraries:

1. By default, Content type option is disabled at the list/library: To enable it: Go to list/library settings-->Advanced settings--> Make it as "Yes" to allow management of content type.
2. By default, Threshold limit for the user:5000 items and for administrators: 20000. These values are hard-coded at the central admin level but Microsoft recommended is should not increase/change the default threshold values to avoid the performance issues.
3. Best practice to handle the threshold: 1) Indexing the columns 2) Avoid threshold exception by maintaining the data/items in a folder structure( SharePoint considers Folder is an item and we can maintain 2000 items in it).
4. Always go with the internal column names(Reason: Display name can be modified but internal can't be modified) to fetch the data and update an items.
5. Go with the creating site columns option rather creating it in each list/library if the same column is used in more than one lists/libraries.
6. Go with the site content types option if more than one site columns needs to preferred in the each lists/libraries.
7. In views, Filter by [Me] if wants to show the results of current logged user only.
8. Upload size limit of files to the document library is: By default: 50MB and max 2GB(SP2013) and max 10GB(SP2016).
9. The files into the library should always be in published mode to get the updated changes by others.
10. By default, SharePoint recommended support for indexing is 20.
11. SharePoint handles the permissions at the lists/libraries and even items level also.
12. Only option to change the list/library URL is through SharePoint designer.
13. By default list/library permissions are inherited from parent but we can have an option to maintain the unique permissions at it.
14. We don't have an option to add users/groups directly at the lists/library level in inheritance mode. If needs, break the inheritance and then add users/groups.
15. Users should have minimum "contribute" level permissions to make CRUD operation at the list/library.
16. Steps to support large files upload: 1) Increase the default value(Default: 50MB and Max support: 2GB) to the desired value 2) Increase the IIS request length 3) Increase the IIS connection timeout length. https://angler.wordpress.com/2012/03/21/increase-the-sharepoint-2010-upload-file-size-limit/ 

Please go the below articles for complete details:

RunWithElevatedprivileges

http://sharepointquicksolutions.blogspot.in/2012/11/all-ways-of-runwithelevatedprivileges.html

AllowUnsafeUpdates

http://sharepointquicksolutions.blogspot.in/2012/03/whenwherewhy-use-allowunsafeupdates-in.html

ForDigest Control

http://sharepointquicksolutions.blogspot.in/2012/03/wherewhenwhy-formdigest-control.html

Interviews questions with answers:

http://sharepointquicksolutions.blogspot.in/2013/01/list-vs-library-sharepoint-interview.html

http://sharepointquicksolutions.blogspot.in/2015/07/sharepoint-faqslistvslibrary.html

http://sharepointquicksolutions.blogspot.in/2012/06/content-types-in-sharepoint.html

PowerShell Scripts:

http://sharepointquicksolutions.blogspot.in//search/label/PowerShell

Your valuable suggestions/feedback helps me to give best outputs/results.

SharePoint 2016 tutorials: Class Day2

In Day 1 session, we discussed why  SharePoint technology is now on demand and how much the importance of having an clear idea about on software and hardware boundaries.

In Day 2 session, we will cover the below topics:

1. SharePoint configuration.
2. SharePoint farms and its types. Use of it.(Small/Medium/Large farms).
3. 12/14/15/16 hive folder structure.
4. SharePoint site hierarchy.
5. SharePoint features.
6. web application, Inetmgr, content DB.
7. Real time examples.

Refer the below article for interview questions with answers and also covered with some real-time scenarios.

http://sharepointquicksolutions.blogspot.in/2012/10/sharepoint-interview-questions-and_19.html