Hi
nice article i found on merging content when using document sets ....
http://msdn.microsoft.com/en-us/library/ff519529.aspx
Regards
Bradley
Friday, August 26, 2011
Tuesday, August 23, 2011
TechEd 2011 in Durban ICC
Hi.
So who else will be attending this event ...
It will be taking place in Durban 17th till the 20th of October 2011 ...
Here is a link if more information is required ... http://www.teched.co.za/.
Regards
Bradley
So who else will be attending this event ...
It will be taking place in Durban 17th till the 20th of October 2011 ...
Here is a link if more information is required ... http://www.teched.co.za/.
Regards
Bradley
Thursday, August 18, 2011
Getting a "Created By" field and assigning its value to an SPUser object
Hi.
i always have to get the SPUser object and i always forget so i guess i will document it so i can refer back to it .... here goes ..
SPUser spUser = null;
SPFieldUser field = itemEvent.Fields.GetFieldByInternalName("Author") as SPFieldUser;
if (field != null && itemEvent["Author"] != null)
{
SPFieldUserValue fieldValue = field.GetFieldValue(itemEvent["Author"].ToString()) as SPFieldUserValue;
if (fieldValue != null)
{
spUser = fieldValue.User;
}
}
Nice and simple ...and works like a charm ... :)
Bradley
i always have to get the SPUser object and i always forget so i guess i will document it so i can refer back to it .... here goes ..
SPUser spUser = null;
SPFieldUser field = itemEvent.Fields.GetFieldByInternalName("Author") as SPFieldUser;
if (field != null && itemEvent["Author"] != null)
{
SPFieldUserValue fieldValue = field.GetFieldValue(itemEvent["Author"].ToString()) as SPFieldUserValue;
if (fieldValue != null)
{
spUser = fieldValue.User;
}
}
Nice and simple ...and works like a charm ... :)
Bradley
Tuesday, August 16, 2011
A Microsoft SharePoint Foundation compatible application could not be found
Hi.
this has been a nagging issue with a prestine 2010 Upgrade from 2007 ..
some users were getting the error "The Document could not be opened for editing. A Microsoft Sharepoint Foundation compatible application could not be found to Edit the document."
So i searched through all the articles on Google but all of these were for Sharepoint 2007 with office 2007 or earlier, which did not solve my problem ....
So the solution that solved my problem was to enable SharePoint Support features and you do this by going to Control panel => Programs and features => go to the office installation and click "Change" => then change the following feature SharePoint Support features to "Run from my computer".
once this has been done Restart the computer.....
then go to control panel again and run a REPAIR on the office installation......
restart the computer and you should be good to go ....
this is what worked for one of my clients ....
this has been a nagging issue with a prestine 2010 Upgrade from 2007 ..
some users were getting the error "The Document could not be opened for editing. A Microsoft Sharepoint Foundation compatible application could not be found to Edit the document."
So i searched through all the articles on Google but all of these were for Sharepoint 2007 with office 2007 or earlier, which did not solve my problem ....
So the solution that solved my problem was to enable SharePoint Support features and you do this by going to Control panel => Programs and features => go to the office installation and click "Change" => then change the following feature SharePoint Support features to "Run from my computer".
once this has been done Restart the computer.....
then go to control panel again and run a REPAIR on the office installation......
restart the computer and you should be good to go ....
this is what worked for one of my clients ....
Sharepoint 2010 Orphaned Workflows
Hi.
Orphaned workflows are workflow tasks and those associated items which have been deleted but sharepoint still keeps a tally of the number of workflow instances running.
i remember in MOSS 2007 that we had to write a script in order to remove Orphaned workflows ....
Not anymore and SharePoint 2010 has made it so much easier ....
In order for the orphaned workflows to be deleted all that is needed to be done is to EMPTY the Recycle bins at the SITE level and then at the SITE COLLECTION level.
and presto ... the orphaned workflows have been removed.
Regards
Bradley
Orphaned workflows are workflow tasks and those associated items which have been deleted but sharepoint still keeps a tally of the number of workflow instances running.
i remember in MOSS 2007 that we had to write a script in order to remove Orphaned workflows ....
Not anymore and SharePoint 2010 has made it so much easier ....
In order for the orphaned workflows to be deleted all that is needed to be done is to EMPTY the Recycle bins at the SITE level and then at the SITE COLLECTION level.
and presto ... the orphaned workflows have been removed.
Regards
Bradley
Subscribe to:
Posts (Atom)