Hey there. Welcome to part 3 of my series on SharePoint customisation using JavaScript and web parts.
So here is the lowdown so far. We are trying to find an effective, repeatable way to easily customise SharePoint form pages, so that we can hide fields or form elements when we need to. The goals were to:
- Allow hidden fields based on identity
- Avoid use of SharePoint Designer
- Avoid customisations to the form pages that unghosted the pages from the site definition
So how have we progressed thus far?.
- Part 1 of this series looked at how we can use JavaScript to deal with the common request of hiding form elements from the user in lists and document libraries.
- Part 2 wrapped this JavaScript code into a web part which has been loaded into the SharePoint web part gallery.
So let’s knock the rest of this over and pick up right from we left off…
CleverWorkArounds Coffee requirement of this post depends on how much you hate JavaScript.
Metrosexual web developer 
Socially inept technical guy
[Quick Navigation: Part 1, Part 2, Part 4, Part 5 and Part 6]
Continue reading “More SharePoint Branding – Customisation using JavaScript Part 3”
Hi again.
JavaScript sucks! There I said it. Despite me hating it as a programming language, I can’t deny that in SharePoint, it does have its uses.
CleverWorkArounds Coffee requirement of this post depends on how much you hate JavaScript.
| Metrosexual web developer |
|
| Socially inept technical guy |
|
| Luddite IT manager |
(sorry … why are you here anyway?) |
[Quick Navigation: Part 1, Part 3, Part 4, Part 5 and Part 6]
To quickly recap the first post of this series, we looked at how we can use JavaScript to deal with the common request of hiding form elements from the user in lists and document libraries. The technique demonstrated can be used for columns, buttons and whatever else you want. The method once debugged, is fairly easy to implement with SharePoint designer with and some cut and paste.
But there are several problems with the method that prevent it from getting a better CleverWorkaround rating than “Meh”. They include:
- One size fits all, fields are hidden for all visitors irrespective of need.
- You need to modify the page in SharePoint designer via cut and paste of JavaScript code
- You need to modify auto-generated pages
- You need to modify a page from its site definition
- Insecure, relying on client side to hide content/controls is not a secure solution
Continue reading “More SharePoint Branding – Customisation using JavaScript Part 2”
