Sharepoint is a product developed only for Internet Explorer, and all non-IE users would probably hate Sharepoint, as there are lots of incompatible functions missing out. Recently I found out that non-IE browsers such as Firefox and Chrome are not able to edit Office files directly when clicking on the file link. The data connectivity would not exist because the browser would simply download the file into local folder.
Sharepoint allows users to setup email alerts on any change or adding to a list or libraries. However, the management of the email alert template can be pretty limiting as many users like to know if it’s possible to customize the email alert templates that get sent out by Sharepoint.
Typically, users that are already added to a site collection are displayed in the People Picker. This prevents anyone from using the People Picker to browse a different user directory. However, in a hosting scenario, you do not want end users to be able to search users from Active Directory; you only want the end users be able to search users that are already in the site collection.
Recently we had client experiencing an ugly error when adding a list item, which the error appears to be System.InvalidOperationException: There is an error in XML document (1, 43). Done lots of checks, but just couldn’t figure out why this happened until we found out it’s due to Internet Explorer 9!
User profile management can be a nightmare in Sharepoint 2010 when some users reporting their job title or email address appearing incorrectly in People Picker search tool. This seems to vary if they search on Last name or First name. Depending on the situation, People Picker returns either the correct, up to date profile information or the out of date.
I had been customising Sharepoing theme lately in 2010 version, and i have to say it’s not very fun, mainly due to lack of documentation online and a big change in UI elements comparing to version 2007.
Sharepoint 2010 allows you to optionally upgrade your UI to version 4, which is the new 2010 version or stays as version 3, which uses the 2007 style packages. What was good with 2007’s was that the style packages actually exist in the 12 hives folder, meaning you could actually go and open up the stylesheets and work from there. However with version 4, things turn ugly. Microsoft used the Office theme package (.thmx) to do its styling in Sharepoint.
Sharepoint has a feature that allows us to migrate list data structure and content to a different site so that we do not have to re-create them. This is done through list settings -> save list as template. List template is a powerful function which can save the data structure of a list as well as its content.
I spent quite some time today fixing this problem of accessing a list item in parent web. What I had to do was to access a list item in a parent web, but strangely it kept returning no result, and I made sure the item did exist in the list.
Then I found out it’s due to permission issue. When accessing a parent web’s list items, you have to run your code under elevated privileges mode, otherwise if you debug it you will see that it crashes when trying to access them.
This is an extremely useful function, which allows you to read an Excel spreadsheet and convert its data into a DataTable in C#. With data in a DataTable, we can perform lots of things to it.
Lately we found a very interesting fact of Sharepoint, which I think is worth writing a post about. Although it is very rare that someone will read directly into Sharepoint database to retrieve information, but for some hardcore users, especially with my last post regarding how Sharepoint stores data in backend database, one can easily read into Sharepoint Prod_Content database and do CRUD transactions.