Forum Korisnici često kao pitanja kao što je ovaj:

> Bok,
>
> Molim Vas, ako postoje bilo kakve mogućnosti za izgradnju prilagođeni popis s
> gospodar i detalji putovanja (kao i faktura) bez korištenja InfoPath.
>

SharePoint daje neke out of the box značajke koje podržavaju vrste poslovne zahtjeve kao što je to.

Općenito, one links two lists together using a lookup column. List A contains the invoice header information and list B contains invoice details.

Koristite dodatne popise za održavanje kupaca brojeve, Brojevi proizvoda, itd..

Pomoću web-dijela upita sadržaja (samo u MAHOVINA) and/or a data view web part to create merged views of the lists. SQL Server Reporting Services (SRS) je također dostupna za izvještajno strani je.

Međutim, there are some important limitations that will make it difficult to use pure out-of-the-box features for anything that is even moderately complex. These include:

• Veličina povezanih pretraživanja popisima vs. "Dotjeranost" of the lookup column type. A lookup column type presents itself on the UI differently depending on whether you’ve enabled multi-select or not. In either case, the out-of-the-box control shows all available items from the source list. If the source list has 1,000 predmeti, that’s going to be a problem. The lookup control does not page through those items. Umjesto toga, it pulls all of them into the control. That makes for a very awkward user interface both in terms of data entry and performance.
• Lookups "povući" one column of information. You can never pull back more than one column of information from the source list. Na primjer, ne možete odabrati kupca "12345" and display the number as well as the customer’s name and address at the same time. The lookup only shows the customer number and nothing else. This makes for an awkward and difficult user interface.
• No intra-form communication. Ja sam pisala o tome ovdje. You can’t implement cascading drop-downs, uvjetno uključivanje / isključivanje polja, itd..
• No cascading deletes or built-in referential integrity. SharePoint treats custom lists as independent entities and does not allow you to link them to each other in a traditional ERD sense. Na primjer, SharePoint omogućuje stvaranje dvije prilagođene popise, "Kupac" and "invoice header". You can create an invoice header that links back to a customer in the customer list. Tada, you can delete the customer from the list. Out of the box, there is no way to prevent this. To solve this kind of problem, bi se normalno koristiti događaja vodiče.

On svibanj činiti se pust, but I would still use SharePoint as a starting point for building this kind of functionality. Though there are gaps between what you need in a solution, SharePoint omogućuje nam da ispune one praznine pomoću alata kao što su:

• Događaj rukuju. Use them to enforce referential integrity.
• Prilagođeni stupci: Create custom column types and use them in lieu of the default lookup column. Add paging, poliranje i AJAX značajke kako bi im odgovara.
• BDC. This MOSS-only feature enables us to query other SharePoint lists with a superior user interface to the usual lookup column. BDC can also reach out to a back end server application. Use BDC to avoid replication. Rather than replicating customer information from a back end ERP system, use BDC instead. BDC features provide a nice user interface to pull that information directly from the ERP system where it belongs and avoids the hassle of maintaining a replication solution.

  BDC je MOSS značajka (nisu dostupne u WSS) and is challenging to configure.

• ASP.NET web obrazac: Stvaranje potpuno opremljenog AJAX-enabled obrazac koji koristi model SharePoint objekta i / ili web-usluge u bolje upotrijebiti SharePoint popisima a pruža vrlo osjetljiv korisničko sučelje.

Zadnja opcija svibanj osjećati kao da ste počevši od nule, , ali u obzir činjenicu da SharePoint platforma vas započinje sa sljedećim ključnim značajkama:

• Sigurnosni model s održavanjem.
• Sustav izbornika s održavanjem.
• "Master tablica" (i.e. prilagođeni popisi) sa sigurnošću, izgrađen-in održavanje i reviziju.
• Traži.
• Natrag završiti integraciju alata (BDC).

Ako počnete s novim prazan projekt u Visual Studio, imate puno infrastrukture i vodovod za izgradnju prije nego što dođete blizu onome što nudi SharePoint.

I do believe that Microsoft intends to extend SharePoint in this direction of application development. It seems like a natural extension to the existing SharePoint base. Microsoft’s CRM application provides a great deal of extensibility of the types needed to support header/detail application development. Although those features are in CRM, the technology is obviously available to the SharePoint development team and I expect that it will make its way into the SharePoint product by end of 2008. If anyone has an knowledge or insight into this, molimo vas da ostavite komentar.

</kraj>