Followers

Thursday, August 26, 2010

SharePoint's out-going e-mail with Exchange 2007

http://blogs.msdn.com/b/fooshen/archive/2006/10/08/sharepoint_2700_s-out_2d00_going-e_2d00_mail-with-exchange-2007.aspx

Workflow Activation Properties in Sharepoint

http://jopx.blogspot.com/2007/03/sharepoint-2007-workflow.html

Copying a Sharepoint List Programatically

http://geekswithblogs.net/AnneBougie/archive/2009/01/23/copy-a-sharepoint-list.aspx

http://www.fivenumber.com/copy-sharepoint-list-items-from-one-site-to-another-programmatically/

Using Visual Studio to submit data from Infopath to Sharepoint List

http://www.bizsupportonline.net/infopath2007/how-to-use-visual-studio-workflow-submit-data-infopath-form-sharepoint-list.htm

Sending Emails Using .Net

http://forums.asp.net/t/971802.aspx

Sharepoint Calcualated Formula For Sharepoint

http://intellects.in/2009/03/04/sharepoint-calculated-columns-formulas/

Increasing size of rich text control in Sharepoint

http://nickgrattan.wordpress.com/2008/12/01/increasing-size-of-rich-text-editing-control/

Update Fields like Created By Modified by in Sharepoint Programatically

http://www.moss2007.be/blogs/vandest/archive/2009/04/13/sharepoint-2007-update-system-properties-created-created-by-modified-modified-by.aspx

Error message when you try to attach a file in a custom form on the Web site in Windows SharePoint Services 3.0: “This form was customized not working with attachment"

http://support.microsoft.com/kb/953271/en-us
http://jpy-tech.com/blog/post/Error-message-customized-form-not-working-with-attachment.aspx

Creating Lists using Sharepoint Object Model

http://dotnetdreamer.com/2009/05/26/creating-lists-using-sharepoint-object-model/

Customizing List Item in MOSS 2007

http://msdn.microsoft.com/en-us/library/dd583142(office.11).aspx

Step by Step Tutorial for Creating Workflows for MOSS 2007

http://sergeluca.spaces.live.com/blog/cns!E8A06D5F2F585013!859.entry

Tuesday, August 3, 2010

Hide Left Navigation Panel

http://www.tek-tips.com/viewthread.cfm?qid=1585004&page=5

Thursday, July 29, 2010

change SharePoint logo

http://serverfault.com/questions/72434/change-sharepoint-logo

JQuery for Everyone: Collapse Text in List View BY Paul Grenier

http://www.endusersharepoint.com/2009/02/20/jquery-for-everyone-collapse-text-in-list-view/

Monday, July 19, 2010

Sending an email in Sharepoint Using Javascript and Custom Forms

http://sharepointjavascript.wordpress.com/2009/10/27/send-e-mail-with-javascript/

Sunday, July 11, 2010

JavaScript for SharePoint List field to populate data from query strings

http://sharepointsolutionsrams.blogspot.com/2010/02/following-javascript-is-used-to.html

Edit SharePoint Field properties, including lookup column list association, with client side code only

http://sharepointjavascript.wordpress.com/2010/03/30/edit-sharepoint-field-properties-including-lookup-column-list-association-with-client-side-code-only/

SharePoint Data View Web Part Extension Functions in the ddwrt Namespace

http://msdn.microsoft.com/en-us/library/dd583143(office.11).aspx

SharePoint: Populating Drop Down List Field with Data from Different Site



http://www.endusersharepoint.com/2010/01/25/sharepoint-populating-drop-down-list-field-with-data-from-different-site/

Wednesday, July 7, 2010

Writing Custom Web Services for SharePoint Products and Technologies

http://msdn.microsoft.com/en-us/library/dd583131(office.11).aspx

Tuesday, July 6, 2010

Customizing Sharepoint List's NewForm.aspx "OK" button click

http://yasuanantha.blogspot.com/2010/05/customizing-sharepoint-lists.html

Setting SharePoint Form Fields Using JavaScript

http://www.sharepointhillbilly.com/archive/2009/07/06/setting-sharepoint-form-fields-using-javascript.aspx

How to dynamically populate a drop-down list by calling a Web service in InfoPath

http://support.microsoft.com/kb/826994

Friday, July 2, 2010

Customizing List Item Forms in Windows SharePoint Services

http://msdn.microsoft.com/en-us/library/dd583142(office.11).aspx

Querying SharePoint List Items using jQuery

http://weblogs.asp.net/jan/archive/2009/05/06/querying-sharepoint-list-items-using-jquery.aspx

Programmatically create a custom SharePoint list from a repeating table in an InfoPath web-based form

http://www.bizsupportonline.net/browserforms/programmatically-create-custom-sharepoint-list-infopath.htm

Thursday, July 1, 2010

Autopopulation the list items in the Sharepoint List

It is a real fun working with javascripts in sharepoint.
I came to across writing a script where my users wanted have the people picker autopopulate with the current user Name.

Here is the code guys


_spBodyOnLoadFunctionNames.push("fillDefaultValues");


function fillDefaultValues() {


var qs = location.search.substring(1, location.search.length);


var args = qs.split("&");


var vals = new Object(getUserDisplayName());


var assignedToInput = getTagFromIdentifierAndTitle("div", "", "People Picker");


assignedToInput.innerHTML = vals;


for (var i=0; i < args.length; i++) {



var nameVal = args[i].split("=");


var temp = unescape(nameVal[1]).split('+');


nameVal[1] = temp.join(' ');


vals[nameVal[0]] = nameVal[1];


}


}


function getTagFromIdentifierAndTitle(tagName, identifier, title) {


var len = identifier.length;


var tags = document.getElementsByTagName(tagName);


for (var i=0; i < tags.length; i++) {



var tempString = tags[i].id;


if (tags[i].title == title && (identifier == ""


tempString.indexOf(identifier) == tempString.length - len)) {


return tags[i];


}


}


return null;


}


function getUserDisplayName() {


var tags = document.getElementsByTagName('a');


for (var i=0; i < tags.length; i++) {



if(tags[i].innerText.substr(0,7) == 'Welcome') {


return tags[i].innerText.substr(8,tags[i].innerText.length);


}


}


}



Thanks to SkillCrusher's Blog for putting some light on it
http://blogs.vbcity.com/skullcrusher/archive/2008/04/10/9024.aspx

Monday, May 24, 2010

sharepoint interactive-charts-using-google-visualization-api

http://www.endusersharepoint.com/2010/05/07/sharepoint-interactive-charts-using-google-visualization-api/

Thursday, May 13, 2010

sharepoint-populating-drop-down-list-field-with-data-from-different Site

http://www.sharepointhillbilly.com/archive/2010/01/21/sharepoint-populating-drop-down-list-field-with-data-from-different.aspx

Thursday, May 6, 2010

Creating Status Icons in Sharepoint Using Calculated Field

http://www.sharepointcommunity.com/spcblog/Lists/Posts/Post.aspx?List=2c65cb54%2De012%2D4f00%2D82af%2Df0df90716d38&ID=77

Thursday, April 29, 2010

MOSS 2007 Numbers of site objects that are supported

The following table lists the recommended guidelines for site objects.




Site object

Guidelines for acceptable performance Notes Scope of impact when performance degrades

Site collection 50,000 per Web application Total farm throughput degrades as the number of site collections increases. Farm

Web site 250,000 per site collection You can create a very large total number of Web sites by nesting the subsites. For example, 100 sites, each with 1000 subsites, is 100,000 Web sites. The maximum recommended number of sites and subsites is 125 sites with 2,000 subsites each, for a total of 250,000 sites. Site collection

Subsite 2,000 per Web site The interface for enumerating subsites of a given Web site does not perform well as the number of subsites surpasses 2,000. Site view

Document 5 million per library You can create very large document libraries by nesting folders, using standard views and site hierarchy. This value may vary depending on how documents and folders are organized, and by the type and size of documents stored. Library

Item 2,000 per view Testing indicates a reduction in performance beyond two thousand items. Using indexing on a flat folder view can improve performance. List view

Document file size 50MB (2GB max*) File save performance is proportional to the size of the file. The default maximum is 50 MB. This maximum is enforced by the system, but you can change it to any value up to 2 GB. Library, file save performance

List 2,000 per Web site Testing indicates a reduction in list view performance beyond two thousand entries. List view

Field type 256 per list This is not a hard limit, but you might experience list view performance degradation as the number of field types in a list increases. List view

Column 2,000 per document library4,096 per list This is not a hard limit, but you might experience library and list view performance degradation as the number of columns in a document library or list increases. Library and list view

Web Part 50 per page This figure is an estimate based on simple Web Parts. The complexity of the Web Parts dictates how many Web Parts can be used on a page before performance is affected. Page



The following table lists the recommended guidelines for people objects.



People object

Guidelines for acceptable performance Notes

Users in groups 2 million per Web site You can add millions of people to your Web site by using Microsoft Windows security groups to manage security instead of using individual users.

User profile 5 million per farm This number represents the number of profiles which can be imported from a directory service, such as Active Directory, into the people profile store.

Security principal 2,000 per Web site The size of the access control list is limited to a few thousand security principals (users and groups in the Web site).



The following table lists the recommended guidelines for search objects.



Search object

Guidelines for acceptable performance Notes

Search indexes One per SSPMaximum of 20 per farm Office SharePoint Server 2007 supports one content index per SSP. Given that we recommend a maximum of 20 SSPs per farm, a maximum of 20 content indexes is supported. Note that an SSP can be associated with only one index server and one content index. However, an index server can be associated with multiple SSPs and have a content index for each SSP.

Indexed documents 50,000,000 per content index Office SharePoint Server 2007 supports 50 million documents per index server. This could be divided up into multiple content indexes based on the number of SSPs associated with an index server.

Content sources 500 per SSP* This is a hard limit enforced by the system.

Start Addresses 500 per content source* This is a hard limit enforced by the system.

Alerts 1,000,000 per SSP This is the tested limit.

Scopes 200 per site This is a recommended limit per site. We recommend a maximum of 100 scope rules per scope.

Display groups 25 per site These are used for a grouped display of scopes through the user interface.

Crawl rules 10,000 per SSP We recommend a maximum 10,000 crawl rules irrespective of type.

Keywords 15,000 per site We recommend a maximum of 10 Best Bets and five synonyms per keyword.

Crawled properties 500,000 per SSP These are properties that are discovered during a crawl.

Managed properties 100,000 per SSP These are properties used by the search system in queries. Crawled properties are mapped to managed properties. We recommend a maximum of 100 mappings per managed property.

Authoritative pages 200 per relevance level This is the maximum number of sites in each of the four relevance levels.

Results removal 100 This is the maximum recommended number of URLs that should be removed from the system in one operation.

Crawl logs 50,000,000 Number of individual log entries in the crawl log.



The following table lists the recommended guidelines for logical architecture objects.



Logical architecture object

Guidelines for acceptable performance Notes

Shared Services Provider (SSP) 3 per farm (20 per farm maximum)

Zone 5* per farm The number of zones defined for a farm is hard coded to 5.

Web application 99 per SSP This limit includes the number of Web applications on child farms consuming resources on this SSP.

Internet Information Services (IIS) application pool 8 per Web server Maximum number is determined by hardware capabilities.

Site collection 50,000 per Web application

Content database 100 per Web application

Site collection 50,000 per database



The following table lists the recommended guidelines for physical objects.



Physical object

Guidelines for acceptable performance Notes

Index servers 1 per SSP*

Application servers running Excel Calculation Services No limit

Query servers No limit Because 100 content databases are supported for each query server, the number of query servers required per farm is based on the number of content databases in the farm. For example, if there are 500 content databases in your farm, you will need at least 5 query servers.

Web server/database server ratio 8 Web servers per database server The scale out factor is dependent upon the mix of operations.

Web server/domain controller ratio 3 Web servers per domain controller Depending on how much authentication traffic is generated, your environment may support a greater number of Web servers per domain controller.

Friday, April 23, 2010

Displaying Sharepoint Fields according to the permission

http://spinsiders.com/laurar/2009/01/23/displaying-sharepoint-fields-by-permission-level/

Friday, April 16, 2010

Creating Multiple Views In InfopathForm

http://www.infopathdev.com/forums/p/7554/52199.aspx

Creating a View in Infopath

Introduction to InfoPath-only views


You can design one form template that accommodates two types of users — those who have Microsoft Office InfoPath installed, and those who do not. This type of form template is called a browser-compatible form template. In a browser-compatible form template, any InfoPath features, settings, and controls that won't work in a Web browser are hidden or disabled in design mode (design mode: The InfoPath design environment in which you can create or modify a form template.). That way, you aren't tempted to use them in your design.



When you're ready to share a browser-compatible form template with users, you must publish it to a server running InfoPath Forms Services, and then make it browser-enabled (browser-enabled form template: A browser-compatible form template that has been published to a server running InfoPath Forms Services, and that has been browser-enabled so that users can both display and fill out the form in a Web browser.). If users have InfoPath installed on their computer, then the form will open in InfoPath. If they do not have InfoPath installed, then the form will open in a Web browser. Either way, the form template doesn't include InfoPath features, settings, or controls that won't work in a browser.



If you expect that many of your users will have InfoPath installed on their computers, you may not want to limit the design of your form template to the subset of features that are supported in a Web browser. In this case, you can create two views of your browser-compatible form template. One view will be for users who open the form template in a Web browser. The other view will be used exclusively by users who have InfoPath installed on their computers. This InfoPath-only view will never display in a Web browser. Consequently, you can use InfoPath features in this view that you wouldn't otherwise be able to use, such as user roles or master/detail controls.



In this topic, you will learn how to design a dedicated InfoPath-only view in a browser-compatible form template. In addition, you will learn how to create a rule (rule: A condition or action, or a set of conditions or actions, that automatically performs tasks based on events and values in the form.) that detects whether the user opening the form template has InfoPath installed on their computer. If InfoPath is detected, the user will see the InfoPath-specific view. If InfoPath is not detected, the user will see the browser-specific view in a Web browser instead.



Top of Page



Scenarios for use

Imagine that you work for an insurance company, and that you are designing a browser-compatible form template for processing insurance claims. Your browser-compatible form template must accommodate policyholders who open and fill out the claim form from your company's Web site, as well as internal users who review and approve the data in the claim form. Your expectation is that external users do not have InfoPath installed on their computers and that internal users do have InfoPath. To accommodate users who do and do not have InfoPath installed, you could design two distinct form templates — one that is browser-compatible and one that is not. However, it is easier and more time-efficient to design one browser-compatible form template that includes the following views:



View 1: External, claim-filing view This is the view that policyholders see when they log in to your Web site and open a claim form. Because there is no way for you to know whether a policyholder has a copy of InfoPath installed on his or her computer, the form template must be browser-compatible. That is, you must ensure that the form can be filled out by using a Web browser.



View 2: Internal, claim-processing view This view is for claims processors, who review the submitted claim form and route it to an insurance adjuster for approval. All insurance company employees have InfoPath installed on their computers. Therefore, you can design a dedicated InfoPath-only view for them. Unlike the claim-filing view, which is accessed by policyholders using a Web browser, the InfoPath-specific view never displays anywhere but in InfoPath, and may therefore contain any of the features, controls, and settings that are not available in browser-compatible form template.



Top of Page



Step 1: Add an InfoPath-only view to a browser-compatible form template

To create an InfoPath-only view in a browser-compatible form template, you change a setting in the View Properties dialog box. This setting allows InfoPath users to see the view, but prevents the view from displaying in a Web browser.



Open your browser-compatible form template.

On the View menu, click Manage Views.

Under Actions, in the Views task pane, click Add a New View.

In the Add View dialog box, type a name for the view, and then click OK.

In the Select a view list, double-click the view that you just created.

Click the General tab.

Clear the Show on the View menu when filling out the form check box.

Note Clearing this check box prevents users who do not have InfoPath installed from attempting to switch to the InfoPath-only view.



Select the Allow InfoPath-only features (the view will not be available in Web browsers) check box, and then click OK.

Design your view as you normally would.

You are now able to use many of the features, controls, and settings in your InfoPath-only view that would not otherwise be available in a browser-compatible form template. For example, you are free to use any of the controls in the Controls task pane, as opposed to just the ones that work in a browser. In addition, you will not see any browser-compatibility errors or messages in the Design Checker task pane.



Note Although you can use the majority of InfoPath features in your InfoPath-only view, certain features and settings that apply to the browser-compatible form template as a whole remain disabled or hidden. For example, you cannot enable digital signatures for the entire form template or use script in your view, since one of the views of your form template is browser-compatible.





To add additional InfoPath-only views to your browser-compatible form template, repeat steps 2-9.

Top of Page



Step 2: Display the browser-only view when the browser-enabled form template is opened in a Web browser

In this procedure, you'll learn how to create a rule that dictates the view that the user sees when they first open a form based on your browser-compatible form template. The rule runs when the form is first opened, and after a particular condition is met. The condition in this case has to do with whether users are opening the browser-enabled form template in a Web browser. If they are, then the browser-only view of the form template appears. This view is limited to the set of features that are supported in a browser.



Open your browser-compatible form template containing the InfoPath-only view.

On the Tools menu, click Form Options.

In the Category list, click Open and Save.

Under Open behavior, click Rules.

In the Rules for Opening Forms dialog box, click Add.

In the Rule dialog box, type a meaningful name for your rule, such as Rule 1: Switch to Browser View.

To specify when the rule should run, click Set Condition.

In the first box under Apply the rule when this condition is true, click The expression.

In the second box, type xdEnvironment:IsBrowser(), and then click OK.

In the Rule dialog box, click Add Action.

In the Action list, click Switch views.

In the View list, click the browser view that you want to switch to, and then click OK.

To prevent any rules from running after this rule (for the current event), select the Stop processing rules when this rule finishes check box in the Rule dialog box.

The rule that you just created will run when the form template is opened and the condition you specified — that is, that the user's environment is a Web browser — is met.

Top of Page



Step 3: Display the InfoPath-only view when the browser-enabled form template is opened in InfoPath

Now you will add another rule to your browser-compatible form template. This rule runs when the form is first opened, and after a particular condition is met. The condition in this case has to do with whether the user who is opening the browser-enabled form template has InfoPath installed on his or her computer. If Infopath is installed, then the InfoPath-only view of the form template displays. Because this view is only visible from within InfoPath, it can contain the full range of InfoPath features.



Open your browser-compatible form template containing the InfoPath-only view.

On the Tools menu, click Form Options.

In the Category list, click Open and Save.

Under Open behavior, click Rules.

Click Add.

In the Rule dialog box, type a meaningful name for your rule, such as Rule 1: Switch to InfoPath View

To specify when the rule should run, click Set Condition.

In the first box under Apply the rule when this condition is true, click The expression.

In the second box, type not(xdEnvironment:IsBrowser()).

Click And.

In the first box under the first condition, click The expression.

In the second box, type not(xdEnvironment:IsMobile()), and then click OK.

In the Rule dialog box, click Add Action.

In the Action list, in the Action dialog box, click Switch views.

In the View list, click the InfoPath-only view that you want to switch to, and then click OK.

To prevent any rules from running after this rule (for the current event), select the Stop processing rules when this rule finishes check box in the Rule dialog box.

The rule that you just created will run when the form template is opened and the condition you specified — that is, that the user's environment is InfoPath and not a Web browser or a mobile device — is met.

Thursday, April 15, 2010

Automated backup In Sharepoint

After so much hard work, once you put your site up and running the only thing which worries you is take the regular backups of your site.

If you have a MOSS 2007 installed on your windows 2003/2008 server then there are two steps you need to take care of:

1) ask your IT department to take the mirror image of the server (with installed softwares periodically). There are few softwares available to achieve this.

2) take the backup of all the sites and the content databases which you have created.

As you know, if you go to the central admin-->operations-->backup and restore--> you will find the option of 'backup'. Its so easy isn't it? The thing is, MOSS 2007 does not let you automate the backup process. I mean what if you want to take the backup everyday at one particular time? There is no way currently available in SharePoint central admin to achieve this. So, here I am, coming to the rescue, and writing down this post.

This time I am not alone I am going to take some references from the Technet and other bloggers.

A. create a folder in the c:/ name it "backup_restore"

B. Share this folder and give full permission. (I bet you know how to do that!)

C. Write a batch file which uses 'stsadm' to take the full backup. (you can select the differential backup too, in my case it takes only few minutes to take the full backup, so I used full backup, with -overwrite option) (Ref: Microsoft Technet)

c.1 Click Start, and then click Run.

c.2 Type notepad, and then click OK.

c.3 In Notepad, type the following text:

##################################################################################

@echo off

echo ===============================================================

echo Back up sites for the farm to C:\backup_restore

echo ===============================================================

cd %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\BIN

@echo off

stsadm.exe -o backup -directory "C:\backup_restore" -backupmethod full -overwrite

echo completed

###################################################################################

c.4 In Notepad, on the File menu, click Save As.

c.5 In the Save As box, select the folder where you want to keep your batch file.

c.6 Using the ".bat" file name extension, type the name of the file in the File name box, for example, backup_batch.bat.

c.7 In the Save as type box, click All files.

c.8 Click Save.

D. Right click on that file and click on open, it will run a script written in a batch file. Most-likely you will get an error : "BACKUP failed to complete the command BACKUP DATABASE SSO. Check the backup application log for detailed messages."

solution: open the SQL server where your content database is stored and create one empty database named 'SSO', run the script again and It will not prompt for any error.

E. Schedule a backup (Ref: Microsoft Technet)

e.1 Start the Scheduled Task Wizard, and then click Next.

e.2 Click Browse, navigate to the batch file that you just created, and then click Open.

e.3 Type a name for your task, for example, backup_batch.

e.4 Select how often you want this task performed (for example, weekly), and then click Next.

e.5 To automatically perform this backup periodically, select an interval such as Weekly or Monthly. To perform this backup one time, or to delay a single backup, select One time only.

e.6 Choose a time and start date for your backup.

e.7 Type a name and password for a user, and then click Next. This task will run as if it were started by that user.

e.8 Click Finish.

F. so, its that easy huh??!!(took 4 hours to put all these together!) Its a good practice that when you take a backup, no one is changing anything in the site, otherwise, there is a possibility that you will get corrupted backup which may not be restored successfully. Follow this link:

http://technet.microsoft.com/en-us/library/cc262811.aspx It will guide you how to apply a read only lock on your sites for the period of time when you are taking backups.

G. Its a good practice to store the files to a different server, I am working on that stuff (Take the SP backup to a different server using FTP) and will add to this post soon.

Enjoy!!!!!!!!!!

Wednesday, April 14, 2010

User list in infopath via the People web service

User list in infopath via the People web service



There has been a tricky problem in infopath for a while trying to get a user list in a drop down box. You can do this with the people web service. The problem has been it is almost impossible to find documentation on the thing and you have to know a few tricks to get it to work. Here are the steps from within Infopath.

Note: It only pulls people that have been to your sharepoint top level site.



1. Go to Design Tasks

2. Click on Data Source

3. Click on Manage Data Connections...

4. Once you are in the Data Connections Dialog box click Add

5. Choose Create a new connection and select Receive

6. Click Next

7. Choose Web Service

8. Click Next

9. Enter the url of the people.asmx web service (i.e. http://yoursite/_vti_bin/people.asmx)

10. Click Next

11. Choose Search Principals from the Select an operation: box.

12. Click Next

13. You are going to want to set the values for parameters.

14. tns:searchText should be your domain with a \ behind it (i.e. domain\)

15. tns:maxResults* should be a number greater than the results (i.e. 1000)

16. tns:PrincipalType should be the word User

17. click Next

18. click Next and then click Finish

19. Now you can click Close to close the Data Connection Dialog Box

20. Place a Drop-Down List Box on the form.

21. Under List box entries choose Look up values from an external data source

22. Choose SearchPrincipals as the data source.

23. Click on Entries

24. Expand until you see Principal Info and choose it

25. Choose DisplayName for DisplayName and whatever field you want for Value (i.e. AccountName or DisplayName)

Monday, April 12, 2010