SharePoint4us

Hi Friends,

ASP.NET provides a configuration system we can use to keep our applications flexible at runtime. In this article we will examine some tips and best practices for using the configuration system for the best results.

The <appSettings> element of a web.config file is a place to store connection strings, server names, file paths, and other miscellaneous settings needed by an application to perform work. The items inside appSettings are items that need to be configurable depending upon the environment, for instance, any database connection strings will change as you move your application from a testing and staging server into production.

As an example, let’s examine this minimal web.config with an appSetting entry to hold our connection string:



Some applications will duplicate these lines of code in many places. If we think about how the above code will evolve over time, we might see a handful of weaknesses. First, we have a hard coded string in place to fetch connection information from the web.config. Hard coded strings can be easy to mistype and difficult to track down if the key ever changes. Secondly, the code will tie us forever to the appSettings section of the web.config file. Although web.config is designed for just such a setting, we might find in the future that we need to pull configuration settings from a database, or change a setting from being application-wide to being a per-user configuration item kept in the Session or in a cookie.

Hi friends,


In this article we can explore a common scenario which can be solved using OOB feature of SharePoint 2013.

Scenario

You have a list to track expense claims. Multiple employees are using the same list. Following are the challenges:
1. Employees should see only their items
2. Employees should not be able to edit other employee’s items

Solution
Although using “views” will be the first solution in mind, we can solve this through OOB way using:
· List Item Level Permissions

Steps

Create an Expense list as shown below.


1. Create 2 users
2. Use 2 browsers
3. Add one expense-item for each user
4. You can see user-1 can see only his/her item
5. Same applies to editing as well
When user 1 logs in:

Hi friends,

Thanks for visiting my blog..

Today in this Post  , I  would like to explain about

                "How to enable Developer Dash Board in SharePoint 2013 ?"

1.  What is Developer Dash Bord and  use of it?
2.  How to enable to your site and check it ?
3.   How many ways to Enable DDB ?

• -Open  "Windows +R" -->CMD
•  Goto the Path "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\BIN"
• Paste this command "stsadm -o setproperty -pn developer-dashboard -pv ondemand"
• -Once this Command is executed ...Please go to your site and check ,you can able to see small icon on the right top side of the master page.
•  It  diplays a page with all the details of the current page .

Hi Friends,

Thanks for visiting my blog...

In this i would like to describe about  SharePoint 2013 newly introduced  features.

• No Internet Explorer 7 support.
• With the purchase of Yammer, there is more emphasis on social media.
• Licensing: Internet sites no longer require an expensive licence, the cheaper standard server licence means that customers can host their internet and intranet on the same platform, reducing costs and providing more flexibility.
• Records and document management: no real change.
• Greater adoption of internet and open standards, enabling broader device support and integration with other services.
• Users can have SharePoint on premise, in the cloud, or a hybrid of both.
• The core ‘Search’ capability, based on FAST technology, is much richer.

• End users can “share” files with others more simply
• Better developer support
• New database storage reduces the overhead of versioned documents
• With Office Web Apps one can now edit documents on iOS devices
• Much more flexibility around images
• Video support improvements.

• Most customers will want to virtualise the SharePoint servers but they are resource intensive so should not be run on over committed hosts
• Beware of remote access requirements, which can cause slow access
• There’s no need to keep scanned and read-only files in SharePoint – it’s an expensive form of storage – it’s better to have a link to these resources in SharePoint
• Don’t underestimate the technical skills that SharePoint needs.
• Some of the SharePoint features require that other infrastructure and client components are all on the 2013 version. Fortunately SharePoint 2013 still allows to run 2010 sites, which means that one can leverage some new features like search, while continuing to use 2010 document libraries for Office 2010 users. This ability to run both in parallel is a key feature introduced in 2013 to help reduce the upgrade pain.

Hi friends,

Thanks for visiting my blog.


In this Post i would like to describe about "SharePoint Workflows".

•   Introduction to workflows.
• .Why we need Workflow?
•  Common Workflow Scenario.
•  Reusable and Non-Reusable Workflows.
•  Typical Workflow Usage in SharePoint
• Designer, Visio and Visual Studio
• Declarative & Compiled Workflows
•  Out of the Box Workflows

 Introduction to workflows.

            Workflows help people to collaborate on documents and to manage project tasks by implementing business processes on documents and items in a Microsoft Office SharePoint Server 2007 site. Workflows help organizations to adhere to consistent business processes, and they also improve organizational efficiency and productivity by managing the tasks and steps involved in business processes. This enables the people who perform these tasks to concentrate on performing the work rather than managing the workflow.

                                        

Why we need Workflow?

Workflow provides a convenient way to automate manual business processes.

The activities in the Workflow can be represented in a graphical manner and adds great flexibility to a developer and non-developer. Using Workflow we can easily achieve the branching, cases and executions in an easier manner

Common Workflow Scenario

We can apply Workflow for the following scenarios.

Scenario 1: A task list allows creation of task for users. Whenever a new task is created in the list, we need to notify the user associated with it. We can use Workflow to accomplish this easily.

Scenario 2: A company consists of developers with various skill sets. There is a set of Training Items. Each developer can apply for the training. The application will be notified to the Training Manager. He can check the skill set and approve or reject the applicant. If selected, the applicant can attend the training. On completion of training there is a verification exam to be undergone by the attendee. If he passes then Certificate is issued else the notification through email is done. We can use Workflow to accomplish this easily.

Scenario 3: People upload their expense reports into a Document Library. The library captures the expense as a separate field. Every week manager has to change status to Approved for the expenses with less than $ 500. The list contains hundreds of entries. The status updation can be done using Workflow in just 1 minute.

Scenario 4: Client can create a bug and it should be notified to Developer through email. Developer on completion of the bug fix changes the status and the Client gets notified. This whole process can be done through Workflow in an easier manner.

Reusable and Non-Reusable Workflows

In the case of SharePoint 2007 the workflow created for one list cannot be used for another list. But in SharePoint 2010.2013  the same workflow can be applied for multiple lists and thus making it Reusable. We can create reusable workflows using SharePoint Designer 2010,2013

Typical Workflow Usage in SharePoint

• Developer creates the Workflow.
• Administrator deploys the Workflow
• Site Users use the Workflow.

Designer, Visio and Visual Studio

The SharePoint Designer provides an easier way for Administrators and Developers to create Workflows. Along with Microsoft Visio, Designer provides much more flexibility and features in Workflow creation.

Using Visual Studio developers can write more complex programming tasks with Workflow. Using the SharePoint extensions for Visual Studio, the inbuilt templates provide easier Workflow creation and deployment.

Declarative & Compiled Workflows

The workflows created using SharePoint Designer are known as Declarative workflows.

The workflows containing code and contained inside DLL files are known as Compiled workflows. They are usually created using Visual Studio 2010. 

Workflow Creators

·         A workflow can be created by:

·         Administrator

·         Developer

·         Power User

·          

Workflow Association

·         A workflow can be associated with the following:

·         Content Type

·         List / Library

·         Site

This makes easier to understand that a Workflow can be started manually or automatically.

Workflow Forms

Following are the types of forms associated with workflow:

1. Initiation Forms are shown to user when they start a workflow. The initiation form is used to capture parameters associated with a workflow.

Examples of parameters include Receiver Email list, Maximum Amount etc.

2. Association Forms are used to associate a workflow with a particular list or content type. The association form is by the Administrator.

In reality the Initiation form can be the same as Association form. The user can override the Association form settings using the Initiation form.

We can provide custom Initiation & Association forms using InfoPath as well.

                          Out of the Box Workflows

Following are the Out of the Box Workflows in SharePoint 2010:

·         Three-state

·         Disposition Approval

·         Collect Signatures

·         Collect Feedback

·         Approval

Hi friends,

Thanks for visiting my blog .

In this post, i would like to describe about "Getting multiple users from SharePoint list Programatically".

Scenario : 
I came across a situation where i want to fetch the usernames and email IDs   from list (Column is people Picker and Check the "allow multiple users" option).

Solution : 

Please find the the below code snippet
*********************************

 SPFieldUser UsersColumn = (SPFieldUser)lstNewPrsReq.Fields.GetField("ColumnName");
 SPFieldUserValueCollection Users = (SPFieldUserValueCollection)UsersColumn.GetFieldValue(lstitemCollection[0]["ColumnName"].ToString());   
   if (Users != null)
     {                                 
  foreach (SPFieldUserValue user in Users)
               {
                        SPUser spUser = user.User;                    
                        if (spUser != null)                                               
                        strCCEmail = strCCEmail + ";" + spUser.Email;
                }                                                                           
          strCCEmail = strCCEmail.TrimStart(';');                             
     }      


strCCEmail : This string contains all the mail ids of the users for that particular list item.

hope this blog helps you........

Hi friends,

Thanks for visiting my blog .

In this post, i would like to describe about "Disable throttling of List in SharePoint".

Scenario : 
I came across a situation where i want to fetch the list items  from list (consists of more than 2 lakhs).

Problem :
 when am pulling the items from the list it showing an error saying that you cannot pull items from list as it exceeds list threshold limit (by default 5000 in central administration  we can see the limit and increase but increasing here is not a good practice ).

Solution : 
we can disable  throttling limit  for particular list in which you want to query the items.
we can do this  by using powershell and object model to my knowledge.


PowerShell Script :
****************************
$web = Get-SPWeb "Site Url"
$list = $web.Lists["ListUrl"]
$list.EnableThrottling = $false
****************************

Paste in notepad and save as ".ps1 " .
1.Open the Management Powershell command prompt (run as administrator).
                 2. Execute the .ps1 file here.
                 3. Go back to the logic and try to query the list items .


Thank you hope this post helps you in understanding 

Hi Friends,

Thanks for visiting my posts,

In this Post , i would like to post about stored procedure in SQL Server.

1.What is stored procedure ?
2. How to Create a stored procedure ?
3. How to Execute a stored procedure ?


 stored procedure 

A stored procedure is a group of sql statements that has been created and stored in the database. Stored procedure will accept input parameters so that a single procedure can be used over the network by several clients using different input data. Stored procedure will reduce network traffic and increase the performance. If we modify stored procedure all the clients will get the updated stored procedure.


 How to Create a stored procedure ?

1. Open Run-->SSMS( SQL Management Studio will get open).

2.   Select the Database and Select the Table on which  you want to write the   
        SP(store Procedure).

3.     In  our case , Database is SAMPLED and Table name is EmpData.
                   


4.    Put Some data into the table.

    
5.    Select New Query  from the ribbon.

 6 . The above screen tells that we have created a SP for  retrieving the table data .

 7 . After creating the Stored Procedure  click on "Execute" in the Ribbon.



How to execute a stored procedure ?

        
 1.  EXEC SP_Name  and execute , you will fetch the data from table 
 



 This is how we create a stored procedure and
  executes a stored procedure.