SharePoint Developers often need to add a custom action to the SharePoint edit control block (ECB). I have had to do this many times myself and since there isn’t a lot of resources available on the subject, I decided to write this post for those who might want to do this sometime, and for myself as a future reference.
I code in several different programming languages and I post content relevant to the different languages on this website. Software development tools and languages evolve very dynamically. What's hot today may be forgotten tomorrow. So, categorizing my content based on language is not very practical. Instead, I use client-server labeling to categorize my work with various programming languages. This section holds content that I consider to be back-end (or server-side) programming.
You may often need to remove HTML tags from some random text block and just display the raw text content. For example you may want to just display the text content of a multi-line rich text value using XSL. But since a multi-line rich text value is internally formatted with html, the html tags will be presented as part of the output.
A while ago, I noticed a peculiar behavior with one of my custom SharePoint workflows. Tasks were getting locked out after the first edit. The first edit proceeds fine but when we attempt to edit the task a second time, we get an error like this:
This task is currently locked by a running workflow and cannot be edited.
Recently, I came across the need to sort the output of some XML transformed via XSLT. Normally, this isn’t too difficult. We just perform the sort within our template with some XSL code as simple as:
The designers of SQL for some reason did not require a keyword (like “ALL”) to protect SQL statements from accidental updates or deletes. Especially when the UPDATE or DELETE statement doesn’t contain a WHERE clause. I wonder if this was deliberate or if it was an oversight. In any case, the programmer becomes “all-powerful”. The significance of this problem will be better appreciated with an example…
The DataGridView is the control that is mostly used for displaying the contents of lists, tables etc. However, the built-in version of this control doesn’t allow for adding row numbers/count via its properties. This feature is often required because it is difficult to keep track of the records in a table with 1000 rows if row numbers are not displayed.