Domino was an amazing collaboration dev environment, but was often misunderstood, at least in both Notes organisations in which I have worked and from the criticisms I have read over the years.
Totally agree re it being a shame, and I still feel that, despite my not having used Domino for about 3 years now. My only role in Domino is now from a support and migration perspective, but I still come across tricks and cheeky hacks which impress.
Notes/Domino is now a dirty word in my organisation - I still experience ignorance about what it does/did, but I don't attempt to correct or inform. I accept that the choice of collaboration platform has changed. In my case, SharePoint 2010 *is* pretty compelling stuff, but it is still messy as Nils says. Better, more RAD than 2007, but still a little messy.
I'll still remain the "last fan" of Notes in my organisation, though, but it's Microsoft all the way now. Doesn't mean I won't keep reading about Notes!
@Jerome B - not sure about the limit on the number of *fields* in a list, but there are recommendations for the number of *list items* in a list. This, for SharePoint 2007 at least, was soft-set to 2000 for rendering purposes, but lists storing higher numbers are possible. Just not recommended. It's better in SharePoint 2010 though.
You *can* change which form to edit a SharePoint list item. Either change it as part of a new list definition (it's a schema XML attribute) or consider changing it in the deployed site using SharePoint Designer.
For multiple subforms, consider these two options (and anyone else chip in with any other ideas!):
- an application page - this is a custom aspx page you create yourself to perform the rendering and can contain whatever logic/controls you like. You are not then restricted to out of the box SharePoint rendering
- use sections in an InfoPath form (assuming you have the enterprise version of SharePoint which allows for InfoPath forms services) and these can have what are called Conditional Formatting (InfoPath 2007) or Rules (InfoPath 2010) applied which hides or displays.
If your Notes form has 2000 fields, and the recommended limit is 256 (check out the limits in 2007 here: http://blah.winsmarts.com/2008-4-SharePoint_limits.aspx), then you might want to consider re-structuring your form. Perhaps you can isolate certain related fields, use a separate form for those and link through to them using a lookup field.
Domino was an amazing collaboration dev environment, but was often misunderstood, at least in both Notes organisations in which I have worked and from the criticisms I have read over the years.
Totally agree re it being a shame, and I still feel that, despite my not having used Domino for about 3 years now. My only role in Domino is now from a support and migration perspective, but I still come across tricks and cheeky hacks which impress.
Notes/Domino is now a dirty word in my organisation - I still experience ignorance about what it does/did, but I don't attempt to correct or inform. I accept that the choice of collaboration platform has changed. In my case, SharePoint 2010 *is* pretty compelling stuff, but it is still messy as Nils says. Better, more RAD than 2007, but still a little messy.
I'll still remain the "last fan" of Notes in my organisation, though, but it's Microsoft all the way now. Doesn't mean I won't keep reading about Notes!
@Jerome B - not sure about the limit on the number of *fields* in a list, but there are recommendations for the number of *list items* in a list. This, for SharePoint 2007 at least, was soft-set to 2000 for rendering purposes, but lists storing higher numbers are possible. Just not recommended. It's better in SharePoint 2010 though.
You *can* change which form to edit a SharePoint list item. Either change it as part of a new list definition (it's a schema XML attribute) or consider changing it in the deployed site using SharePoint Designer.
For multiple subforms, consider these two options (and anyone else chip in with any other ideas!):
- an application page - this is a custom aspx page you create yourself to perform the rendering and can contain whatever logic/controls you like. You are not then restricted to out of the box SharePoint rendering
- use sections in an InfoPath form (assuming you have the enterprise version of SharePoint which allows for InfoPath forms services) and these can have what are called Conditional Formatting (InfoPath 2007) or Rules (InfoPath 2010) applied which hides or displays.
If your Notes form has 2000 fields, and the recommended limit is 256 (check out the limits in 2007 here: http://blah.winsmarts.com/2008-4-SharePoint_limits.aspx), then you might want to consider re-structuring your form. Perhaps you can isolate certain related fields, use a separate form for those and link through to them using a lookup field.
Andrew