Forum gebruikers dikwels as vrae soos hierdie:

> Hallo,
>
> Sê asseblief vir my as daar enige moontlikhede om 'n persoonlike lys op te bou met
> meester en detail tipe (soos fakture) sonder die gebruik van Path.
>

SharePoint bied 'n paar uit die boks funksies wat ondersteun soorte van die maatskappy se behoeftes soos wat.

In die algemeen, one links two lists together using a lookup column. List A contains the invoice header information and list B contains invoice details.

Gebruik die addisionele lyste kliënt getalle te handhaaf, produk getalle, ens..

Gebruik 'n inhoud navraag web deel (slegs in Moss) and/or a data view web part to create merged views of the lists. SQL Server Reporting Services (SRS) is ook beskikbaar vir die aanmelding kant van.

Egter, 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:

• Grootte van verwante lookup lyste vs. "Intelligensie" 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 items, that’s going to be a problem. The lookup control does not page through those items. In plaas daarvan, it pulls all of them into the control. That makes for a very awkward user interface both in terms of data entry and performance.
• Soektogte "terug te trek" one column of information. You can never pull back more than one column of information from the source list. Byvoorbeeld, jy kan nie 'n kliënt kies "12.345" 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. Ek het geskryf oor hierdie hier. You can’t implement cascading drop-downs, voorwaardelik in staat gestel / afskakel velde, ens..
• 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. Byvoorbeeld, SharePoint kan jy twee persoonlike lyste te skep, "Kliënt" and "invoice header". You can create an invoice header that links back to a customer in the customer list. Toe, you can delete the customer from the list. Uit die boks, there is no way to prevent this. To solve this kind of problem, jy nie normaalweg sou geval hanteerders gebruik.

Dit mag lyk donker, 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 ons in staat stel om daardie gapings te vul wat die gebruik van gereedskap soos:

• Event hanteerders. Use them to enforce referential integrity.
• Custom kolomme: Create custom column types and use them in lieu of the default lookup column. Add paging, buffer en om AJAX funksies te maak hulle ontvanklik.
• 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 is 'n MOSS funksie (nie beskikbaar in WSS) and is challenging to configure.

• ASP.NET web vorm: Skep 'n volle funksionaliteit AJAX-enabled vorm wat gebruik die SharePoint voorwerp model en / of web dienste te hefboom SharePoint lyste, terwyl die verskaffing van 'n baie ontvanklik gebruikerskoppelvlak.

Die laaste opsie kan voel soos jy begin van nuuts af, maar kyk na die feit dat die SharePoint platform begin jy met die volgende belangrike funksies:

• Sekuriteit model met onderhoud.
• Menu met onderhoud.
• "Meester tafel" (d.w.z. persoonlike lyste) met sekerheid, gebou-instandhouding en ouditering.
• Soek.
• Terug einde integrasie gereedskap (BDC).

As jy begin met 'n nuwe leë projek in Visual Studio, jy het 'n baie infrastruktuur en loodgieterswerk te bou voor jy naby wat SharePoint bied,.

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, los 'n comment.

</einde>