Stone Coast Web Design Blog

http://office.microsoft.com/en-us/sharepoint-designer-help/use-the-task-process-editor-for-approval-workflows-HA101863538.aspx

http://office.microsoft.com/en-us/windows-sharepoint-services-help/manage-lists-and-libraries-with-many-items-HA010173667.aspx

http://visualstudiogallery.msdn.microsoft.com/e8360a85-58ca-42d1-8de0-e48a1ab071c7

If you need a lookup field in a separate list and the original field is a choice column, then there’s no direct way to do this. In other words,  it’s impossible to map a lookup field on a choice field. There’s a workaround, however, by using a calculated field which copies the information from the choice field. The look up field is then able to map the calculated field’s value.  Here’s a nice article on how to do this:

http://bramnuyts.be/2011/04/05/using-a-lookup-field-on-a-choice-field-workaround/

Source: http://salaudeen.blogspot.com/2012/03/50-limitations-of-sharepoint-sandboxed.html 

1. Deployment at site collection level (No Web Application-scoped Features or Farm-scoped Features). So, If you have 100 site collections, then you have to deploy the same sandbox solution to 100 
site collections. 

2. No SPSecurity - Therefore no Elevated Privileges

3. You can't use SPSite object, So you can't get into other site collections

4. Visual webparts are not supported (But you can use the "Visual Studio 200 SharePoint Power Tools" to get this functionality)

5. cannot call to the network resources. E.g. You cannot read/write to a database on the server (But you can use Silverlight)

6. Only "No code" workflows allowed. No Visual studio workflows (But the workflows without classes which are imported and edited in Visual studio will work!)

7. No support for System.IO, Therefore you Cannot read/write to the file system. 

8. HideCustomAction, CustomActionGroup are not allowed. But you can use <CustomAction>

9. Remember, Resource Usage Quotas/Limits applied on Sandboxed solutions http://msdn.microsoft.com/en-us/library/gg615462.aspx

10. No Feature stapling supported.

11. Can't write to registry (But you can read)

12. Limited Server Object Model MSDN: http://msdn.microsoft.com/en-us/library/gg615454.aspx

13. Can't set cookies in the sandbox. Use JQuery plugin instead http://plugins.jquery.com/project/cookie

14. No call to external WCF/web services such as Facebook (But we can use AJAX)

15. Content Type Binding is not supported

16. No support for custom Timer jobs

17. Can't use SharePoint mapped folders such as _layouts

18. Can't export a Sandboxed Web Part

19. Microsoft.SharePoint.WebControls and Microsoft.SharePoint.WebPartPages Namespace are not available.

20. Managed Metadata - No programmatic access to taxonomy object model. 

21. No ADO.NET support!

22. No support for SPUtility.SendEmail, So you can't Send Mails using this class.

23. No caching support

24. No Custom HTTP Modules

25. No developer dashboard

26. No Site Definition

27. Can't use controls for delegation

28. No Business Connectivity Services support

29. No Localization support

30. No SPWebConfigModification usage

31. Most of the Microsoft.SharePoint.Administration are disabled

32. No Document converters

33. No User Control support.

34. NO Custom service applications 

35. SharePoint web controls (such as SPTreeView) are not supported

36. ClientScriptManager is not available

37. Can't access the event viewer for logging 

38. No PropertyBags of SharePoint Object model are not accessible,( But you can use SPWeb.AllProperties or custom list to store settings)

39. No GAC Deployment, Your solutions will be stored in content database.

40. CustomPropertyToolPart not supported

41. Can't create application pages or site pages with code behind

42. No Server side redirects

43. Can't access some of the enterprise services like UserProfile, Search 

44. Can't access dlls from BIN and resources files(.resx) 

45. Can't access code that is not marked to allow partially trusted callers

46. Can't deploy assemblies to GAC and Cannot call assemblies deployed out of Global Assembly Cache 

47. HttpRequest.Files collection will not contain anything

48. Only SPLimitedWebPartManager is available.

49. SharePoint Web controls (namespace SharePoint.WebControls) are not available,

50. Last but not least: site Template Binding is not supported.

Nice article on the differences between Sandboxed Solutions and Farm Solutions in Sharepoint 2010

http://technet.microsoft.com/en-us/library/ee721992.aspx

http://blogs.msdn.com/b/infopath/archive/2010/06/03/how-to-pass-querystring-data-into-an-infopath-form.aspx

This is a great blog post on how to make filling out InfoPath 2010 forms faster and easier.

http://blogs.msdn.com/b/infopath/archive/2010/07/29/tips-and-tricks-for-making-form-filling-faster.aspx 

Here is my favorite example

Setting up the default user

Setting the default value of the Person/Group picker is done through the fields task pane. Show the fields task pane by selecting “Show Fields” on the data tab and expand your Person/Group picker field (in my case, outBy). Click “Show advanced view” to see the detailed view. Right-click on the AccountId and choose properties.

Under default value, choose the function builder and type userName().
Again, make sure that “Refresh value when formula is recalculated” is unchecked, so that this rule is only run once and not every time the form is opened. Click Ok.

Repeat this process with the DisplayName (optional) to get the best experience. Now the people picker will default to the person who opens the form.
When we load the form, the date, boat type, and checked out by fields are already filled out. With half of the fields completed, it will take employees less time to check out boats.

I was recently trying to display an image in a calculated field column in a Sharepoint list and couldn’t figure out how to output the HTML in that column.  I came across this article which helped me quite a bit. http://blog.pathtosharepoint.com/2008/08/07/calculated-columns/ and http://blog.pathtosharepoint.com/2008/09/01/using-calculated-columns-to-write-html/

Here is the formula I used:

=IF(Status="Green","<DIV><img title='Green' border='0' alt='Green' src='https://fsa.share.ed.gov/teams/bo/SL/SiteAssets/images/Green.gif'></DIV>",
IF(Status="Yellow","<DIV><img title='Yellow' border='0' alt='Yellow' src='https://fsa.share.ed.gov/teams/bo/SL/SiteAssets/images/Yellow.gif'></DIV>",
IF(Status="Red","<DIV><img title='Red' border='0' alt='Red' src='https://fsa.share.ed.gov/teams/bo/SL/SiteAssets/images/Red.gif'></DIV>")))

This is the javascript that must be placed in a Content Editor Web Part below the Web part containing the list above

<script type="text/javascript">
//
// Text to HTML
// Feedback and questions: Christophe@PathToSharePoint.com
//
var theTDs = document.getElementsByTagName("TD");
var i=0;
var TDContent = " ";
while (i < theTDs.length) {
try {
TDContent = theTDs[i].innerText || theTDs[i].textContent;
if ((TDContent.indexOf("<DIV") == 0) && (TDContent.indexOf("</DIV>") >= 0)) {
theTDs[i].innerHTML = TDContent;
}
}
catch(err){}
i=i+1;
}
//
// ExpGroupRenderData overwrites the default SharePoint function
// This part is needed for collapsed groupings
//
function ExpGroupRenderData(htmlToRender, groupName, isLoaded) {
var tbody=document.getElementById("tbod"+groupName+"_");
var wrapDiv=document.createElement("DIV");
wrapDiv.innerHTML="<TABLE><TBODY id=\"tbod"+ groupName+"_\" isLoaded=\""+isLoaded+ "\">"+htmlToRender+"</TBODY></TABLE>";
var theTBODYTDs = wrapDiv.getElementsByTagName("TD"); var j=0; var TDContent = " ";
while (j < theTBODYTDs.length) {
try {
TDContent = theTBODYTDs[j].innerText || theTBODYTDs[j].textContent;
if ((TDContent.indexOf("<DIV") == 0) && (TDContent.indexOf("</DIV>") >= 0)) {
theTBODYTDs[j].innerHTML = TDContent;
}
}
catch(err){}
j=j+1;
}
tbody.parentNode.replaceChild(wrapDiv.firstChild.firstChild,tbody);
}
</script>

This is the result

Additional References:

• http://blog.pathtosharepoint.com/2008/11/01/troubleshooting-your-html-calculated-column/
• https://www.nothingbutsharepoint.com/sites/eusp/Pages/default.aspx?cat=399
• http://office.microsoft.com/en-us/windows-sharepoint-services-help/examples-of-common-formulas-HA010105479.aspx
• http://office.microsoft.com/en-us/windows-sharepoint-services-help/CH010065006.aspx 

http://msdn.microsoft.com/en-us/library/bb862071.aspx