In Sharepoint 2010 when you have notifications turned on users receive notifications by default when tasks are created and when tasks change.
Depending on your workflow requirements this can result in users being flooded with too many notifications. To disable the “Change” notification but keep the original assignment notification you can follow the instructions in this post.
If you want to script it so you can deploy it part of a solution package, or as a powershell script then you can also use Object Model:
SPList workflowtasks = web.Lists[&quot;Tasks&quot;];
workflowtasks.EnableAssignToEmail = true;
//Disable Changed notifications
var alert = web.Alerts.Cast&lt;SPAlert&gt;().FirstOrDefault(i =&gt; i.List.ID == workflowtasks.ID &amp;&amp; i.EventType == SPEventType.All);
if (alert != null)
alert.EventType = SPEventType.Add;
SPMetal is a great tool, of you don’t know SPMetal it’s an ORM tool that maps SharePoint objects to entity classes, it abstracts all of that CAML ugliness with a nice linq provider and it sort of works nicely. But as with almost everything in SharePoint it has its glitches.
I just come across a pretty nasty one. I have this entity that for some reason one of the fields was always returning null, no custom mappings completely auto-generated like the rest of my entities.
I have checked the generated CAML and the field is part of the viewfields parameter as expected. After a bit of debugging i realised that the internal field name didn’t match the one SPMetal was using to build the CAML. The reason is that apparently SharePoint truncates the internal field name if its length exceeds 32 characters. Now this should be fine but apparently SPMetal developers decided to hardcode the logic of conversion from display to internal, instead of querying the internal name when generating the entities. So a field named “Tools and Websites Link”, will be named internally as “Tools_x0020_and_x0020_Websites_x1”, and SPMetal will generate it as “Tools_x0020_and_x0020_Websites_x0020_Link”. Yep nasty.
There is a couple of solutions here, the most obvious one is to make your field name smaller, bear in mind that if you have spaces in your field name SharePoint replaces them with _x0020_ so if you have a lot of spaces you are guaranteed to hit this limit.
Another workaround is to manually set the internal field name as show in this post.
There are multiple posts about setting up a SharePoint project building in a continuous integration server. One of the challenges assuming that SharePoint is not installed on the build server (as it shouldn’t) is to provide the necessary SharePoint assemblies for the build to happen. This is where out problems begun.
We decided to copy the libraries from 14ISAPI and keep them under source control for better portability. We could have installed them in the GAC witch would allow us to run multiple SharePoint project builds without having to provide all the necessary dlls all the time.
After getting all the assemblies and changing the references in the project to point our local versions we got several compilation errors building the project:
The type or namespace name 'Office' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?
The type or namespace name 'Publishing' does not exist in the namespace 'Microsoft.SharePoint' (are you missing an assembly reference?)
The type or namespace name 'Taxonomy' does not exist in the namespace 'Microsoft.SharePoint' (are you missing an assembly reference?)
What stumped us is that we are including all those references. After spending an entire day trying different things we came across the problem. Publishing has a dependency on
Nothing on the error messages refer to this namespace. So After including the following library:
C:Program Files (x86)Microsoft Chart ControlsAssembliesSystem.Web.DataVisualization.dll
The project compiled as expected.
SPSearch4 is the service name for the SharePoint Foundation Search service. It is considered a best practice to run this service with an account other than the farm account. But where do you change it?
Usually you would change it in Central Administration > Security > Configure service accounts. But if you are reading this you probably have figured that SharePoint Foundation Search is not part of the available services you can pick on the list.
To configure the credentials you need to do it from here:
System Settings > Manage services on server > SharePoint Foundation Help Search