Contents tagged with Office System
-
SharePoint Designer 2007 Governance: Options for selective lockdown?
Stephen from SharePoint Designer Team had lately published a great article about options available to users for locking down SharePoint Designer 2007 (SPD). I review & re-visit that list to evaluate requirements missing, and what can be done by a developer to fill the gap of “selective lockdown”.
-
SharePoint vNext and/or Office 14 - Master Data Management!
June 7th 2007 - Microsoft announced merger of data management company, Stratature. Stratature was bought for its flagship product, Enterprise Dimension Manager (+EDM), which had growing customers base in a vertical which is quite new to the "connected enterprise". Post merger, Microsoft pulled off +EDM from the market and continued support to existing customers. +EDM was a new category of product line, which company defines as Master Data Management vertical.
-
SharePoint Forms - Improve layout of Field's 'description' to save screen-space and enhance UX
Default Forms in SharePoint leave you with limited choice sometimes when it comes to customization. One such thing is location of fields Description under the control, instead of under fields Title on the left. That's unlike most other system forms in Central Admin or throughout Application Pages. This leaves users with more screen utilization vertically, leaving empty spaces on left. So I think most users do not describe their form fields to keep them usable, while on flip-side it definitely makes forms hard-to-guess for others, particularly so when there are many columns in a list.
-
How to customize rendering of SharePoint list form fields - Part 1
While SharePoint offers great flexibility to users for quickly creating custom lists in various forms, flexibility of forms and fields rendered within is fairly limited on WSS/MOSS UI. In this series, I aim to share some of my findings and, perhaps, come up with wish-list for "SharePoint 2009"!
-
Showing Child-Items Count in hierarchical SharePoint Lists with multiple content-types
SharePoint 2007 introduced content-types to template standard record definitions and re-use them across lists, such as Task, Issue, or even Folder. Multiple such content-types can be set associated to a single list. A folder is a content-type as well, and it can not only have child items/files within it but also have extended columns just like any item. This allows interesting scenario's where-by instead of using Lookups to setup relationship of items spread across lists one can implicitly set master-detail relationship on items within same lists.