Suas chun dáta (04/2008): Léiríonn an iontráil seo bhlag iontach cur chuige dea-javascript bunaithe ar an bhfadhb seo: http://webborg.blogspot.com/2008/04/add-functions-and-events-to-sharepoint.html
Suas chun dáta II: (04/2008): Breathnaíonn an iontráil seo blog bhfuil tuar dóchais inti chomh maith: http://www.cleverworkarounds.com/2008/03/13/free-mosswss-2007-web-part-hide-controls-via-javascript/
Roinnt uaireanta sa tseachtain, más rud é nach laethúil, forum users describe a requirement that would normally be met via cascading drop-downs. Mar shampla, Tá mé dhá rialuithe titim síos-:
- Liosta de U.S. stáit
- Liosta de U.S. cities.
As responsible UI providers, we want it to operate like this:
- Paul selects a U.S. state from the drop-down.
- This causes the cities drop-down to filter only those cities that belong to the selected state.
- Paul selects a city from this filtered list.
There is no out-of-the-box support for this feature. Go deimhin, there is no OOB support for any kind of direct intra-form communication. This includes programmatically hiding/enabling/disabling fields in response to field changes elsewhere on the form.
The real objective of this article to to describe possible solutions and these are the options as I know them:
- Develop a custom column type. As a custom-column-developer, you have full control over the "world" of that custom column. You can implement a cascading drop-down that way.
- Consider using workflow. In some cases, you want to automatically assign a value to field based on another field’s value. Sa chás seo, you would normally try to use a calculated column, but some times, it just won’t get the job done. SharePoint Designer workflow is a relatively administer-friendly alternative to dropping down into code and visual studio. If you go this route, be aware of the issue addressed by airteagal seo (http://paulgalvin.spaces.live.com/blog/cns!CC1EDB3DAA9B8AA!405.entry).
- Event handlers: Like workflow, this is an after-the-fact solution. Your event handler is a .NET assembly (C #, VB.NET) to which SharePoint passes control. The object you develop has access to the data of the list (and the whole object model) and can do any needed calculation.
- Use SharePoint Designer to create custom entry forms. I don’t have direct experience with this approach, but I hear they are doing good things with NewForm.aspx these days 🙂
- Roll your own ASP.NET data entry function (as a stand-alone web page or as a web part) and use that instead.
If anyone knows other and/or better options, please post a comment and I’ll update the body of this post.
<deireadh />
Paul,
Check this out: http://www.spsdev.com/filter.aspx .
From their site: "SpsDev.Com’s Filter Field is a custom field type that does filtering.
You can add one to many filter fields to your list or library, and each one can
be filtered based on another filtered field in the list. Pick a state in
one field, and the list of cities in the next field is filtered to only show
items from that state, mar shampla. In this release we support SQL Server
2000 agus 2005, and Xml as sources for the field data. As you change a
selection in any of the drop downs, all of the drop downs below it are each
filtered to show only the appropriate choices based on the selection that’s
been made."
– Monjo