Standard disclaimer – the ‘migratenotes’ posts come from a Notes Migration blog that I wrote from 2007-2010. More Info
I had mentioned quite some time ago that one feature SharePoint just didn’t have was hide-when formulas.
Let me state here and now that I was mistaken.
Just this morning, I figured out how to do hide-whens in SharePoint. I don’t have the full range of options provided by the @Functions in Notes, but I can hide form UI based on data within that form.
I will try to expand on this later (I’ve already got 3 topics lined up to post about… just need to find the time), but in brief:
- Edit your list pages in SharePoint Designer (NewForm.aspx, etc)
- Hide the default list web part on that form. (Apparently it must be hidden, not deleted… i haven’t tested to see why that is.)
- Add a Custom List Web Part to the form
- Modify the XSL in that new web part.
That’s it. Now that you are working in XSL, you can use xsl:if to write logic to choose exactly what UI components should / should not display.
This technique won’t give you the full capabilities of Domino’s hide-whens, as it limits your logic to the list data… but that is better than nothing, and still fairly powerful. I intend to do more research to see if I can pull in more environment/session/user data to expand the capabilities of this concept.
And I suppose this also means I need to become much stronger with XSLT. I’ve suspected for years that XSLT is a skill I need to pick up. This forces the issue.