UPDATE (04/2008): Bu, böyük blog giriş bu problemi yaxşı bir javascript əsaslı yanaşmanı göstərir: http://webborg.blogspot.com/2008/04/add-functions-and-events-to-sharepoint.html

YENİLƏNİB II: (04/2008): Bu blog giriş, eləcə də perspektivli görünür: http://www.cleverworkarounds.com/2008/03/13/free-mosswss-2007-web-part-hide-controls-via-javascript/

Bir neçə dəfə bir həftə, gündəlik əgər, forum users describe a requirement that would normally be met via cascading drop-downs. Məsələn, Mən iki açılan nəzarət:

• U.S siyahısı. dövlətlər
• U.S siyahısı. şəhərlər.

Məsul UI təminatçıları kimi, biz bu kimi fəaliyyət istəyirəm:

• Paul bir U.S seçir. state from the drop-down.
• This causes the cities drop-down to filter only those cities that belong to the selected state.
• Paul bu süzgəcdən siyahıdan bir şəhər seçir.

There is no out-of-the-box support for this feature. Faktiki olaraq, 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.

Bu maddəyə əsl məqsədi mümkün həll yolları təsvir etmək və onların bildiyiniz kimi bu variantları:

1. 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.
2. Consider using workflow. In some cases, you want to automatically assign a value to field based on another field’s value. Bu halda, 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 Bu maddənin (http://paulgalvin.spaces.live.com/blog/cns!CC1EDB3DAA9B8AA!405.entry).
3. 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.
4. 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 🙂
5. 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.

<Tamamlama />