List Attachments over 50MB need more than an increase in Maximum Upload Size... - Brett's SharePoint Blog - Site Home - MSDN Blogs

http://blogs.msdn.com/b/bgeoffro/archive/2008/03/19/list-attachments-over-50mb-need-more-than-an-increase-in-maximum-upload-size.aspx

Basically there's a setting maxRequestLength in web.config file at the IIS level that will block list attachment uploads above 50MB. maxRequestLength="204800" would allow list attachment up to 200 MB.

How to debug InfoPath 2010 browser enabled form with code behind

Here is a step by step instruction by Nik Patel. The instruction works beautifully. It is the best instruction on this topic I have found so far.

Step by Step – Debug InfoPath 2010 Forms Deployed on SharePoint 2010 Using Visual Studio 2010

Understand, scale and monitor Crawling / Processing / Indexing in FAST Search for SharePoint

Greate blog entry on this, good read and links to other resources.

Understand, scale and monitor Crawling / Processing / Indexing in FAST Search for SharePoint by leonardocsouza

Very other helpful information on SharePoint Search, Fast Search for SharePoint too. 

"relative links" Error when verifying/uploading infopath 2010 form template

Got the following error message when trying to deploy an infopath 2010 form template with code via central administration to production:

“Relative links to Data Connection Libraries located in different SharePoint Site Collections are not supported.”


Google search found the following blog 

Relative Links” Error Message when verifying an InfoPath Form Template by Rob Finney

In summary, the url to the SharePoint site needs to be exactly the same, including upper/lower cases, in the data connection settings. So to fix, just delete the offending data connection, add it back, then convert it to data collection file, at this step, ensure the url is correct and the capitalization of each letter is exact the same as the other data connections.

How to make custom user profile properties searchable in SharePoint 2010?

Not as simple as in MOSS, please see the post by Steve McDonnell

Making Custom User Profile Properties Searchable in SharePoint 2010

SharePoint 2010 Blog - Antonio Lanaro: SharePoint 2010 Fast Search: Filter all contents w...

SharePoint 2010 Blog - Antonio Lanaro: SharePoint 2010 Fast Search: Filter all contents w...: "OBJECTIVE : To programmatically obtain the URL to access the FAST search and return contents filtered by Metadata. To enable a custom search..."

Create a Search Scope for FAST Search for SharePoint 2010

Please see "Creating a Scope in FAST Search for SharePoint 2010"

Basically, you can't use SharePoint CA to accomplish this task, you have to use PowerShell scripts.

Delete All Items, including Folders, from SharePoint List Programmatically and Efficiently

From this post http://www.praveenmodi.com/programmatically-delete-all-items-sharepoint-list/ by Praveen Modi.

///

/// Purges items and folders from a list
/// Define WSSV3 to remove list folders
///

/// The SPList you want to
/// purge items from
private static void PurgeList(SPList list)
{
Console.WriteLine("Purging list: " + list.Title);
Console.WriteLine("Base Type: " + list.BaseType.ToString());

// ===========================================================
// list.ItemCount returns a count that includes all items
// "AND" folders.
// You can't use list.Items.DeleteItemById() to remove a
// folder
// ===========================================================
System.Collections.Hashtable hItems =
new System.Collections.Hashtable(list.ItemCount);

// ===========================================================
// SPList.Items returns all list items in the entire list
// regardless of folder containment
// Note, just because list.ItemCount includes folders,
// list.Items does not.
// ===========================================================
foreach (SPListItem item in list.Items)
hItems.Add(item.ID,null);

// Remove the list items
foreach (int ID in hItems.Keys)
list.Items.DeleteItemById(ID);
// Clear the hashtable
hItems.Clear();
// ===========================================================
// SPList.Folders returns all folder items in the entire list
// regardless of parent folder containment
// ===========================================================
foreach (SPListItem item in list.Folders)
hItems.Add(item.ID,null);

// Remove the folder items
foreach (int ID in hItems.Keys)
{
list.Folders.DeleteItemById(ID);
}
}

Expiration Policy Timer job does not seem to run

Copied from this post: http://ithinksharepoint.blogspot.com/2009/03/expiration-policy-timer-job-does-not.html

beginning-of-copy

The policy is run once a day, however fortunately you can start it manually. Using Central Admin->Operations->Information Management Policy Configuration, I clicked on the Expiration policy link. Then within there clicked "Process Expired Items Now". Looked at the Timer Job Status (Central Admin->Operations->Timer Job Status) and there was no reference of the Expiration Policy.

Looked within Timer Job Definitions (just under the Timer Job Status link) and a timer job had been created called "Expiration Policy (manually initiated)" but it had never been run. Actually neither had the daily "Expiration Policy". I went back to the Information Management Policy Configuration and into the Expiration policy. The "Process Expired Items Now" button was greyed out, to clear this I ended up deleting the "Expiration Policy (manual initiated)" timer job. This enabled the "Process Expired Items Now" button... however nothing.

Other things that I tried included stsadm -o execadmsvcjobs - though nanda.

Then I thought about the fact that the job had never been run and I found this article
http://www.sharepointblogs.com/teameli/archive/2008/10/13/record-center-information-management-policy-jobs-not-running.aspx

Following the instructions sorted the problem...

end-of-copy

CAML Query returns all items

I use CAML Query Builder a lot, a great tool. However, I ran into a situation that the CAML query returns all the items of a list. Thanks to Google, I found a blog entry by Steve Pietrek. His suggestions fix the problem.





Specifically, I did the following:

1. remove the opening and closing query tag
2. change the double quote to single quote in the query.