Стандард ВСС / Мос унос података екрани не подржава каскадно падајуће (или други од комуникације унутар)

УПДАТЕ (04/2008): Овај велики блога показује добру Јава Сцрипт приступ овом проблему: http://webborg.blogspot.com/2008/04/add-functions-and-events-to-sharepoint.html

Ажурирање ИИ: (04/2008): Овај блог унос изгледају обећавајуће и: http://www.cleverworkarounds.com/2008/03/13/free-mosswss-2007-web-part-hide-controls-via-javascript/

Неколико пута недељно, ако не свакодневно, forum users describe a requirement that would normally be met via cascading drop-downs. На пример, Имам две падајуће контроле:

  • Списак У.С. државе
  • Списак У.С. 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. Заправо, 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.

Стварни циљ овог чланка да опише на могућа решења и то су опције као што их знам:

  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. У овом случају, што то обично покушати да користе израчунате колоне, али неки пута, 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 овај чланак (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, али чујем да ових дана чине добре ствари са НевФорм.аспк 🙂
  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.

<крај />

4 мисли о "Стандард ВСС / Мос унос података екрани не подржава каскадно падајуће (или други од комуникације унутар)

  1. Паул Галвин
    Моњо,
    Thanks for the comment, this is the kind of feedback for which I was hoping.
    It appears that as I write this, the cost is $349 USD? Ако је тако, is that price for unlimited use?
    Хвала!
    –Павле
  2. Мајк Монгеау

    Павле,

    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, на пример. In this release we support SQL Server
    2000 и 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."

    Моњо

Леаве а Репли

Ваша емаил адреса неће бити објављена. Обавезна поља су означена *