Utenti forum spiss bħala mistoqsijiet bħal din:

> Hello,
>
> Jekk jogħġbok għidli jekk hemmx xi possibbiltajiet biex tinbena lista dwana ma
> kaptan u dettall tip (bħal fatturi) mingħajr l-użu InfoPath.
>

SharePoint jipprovdi wħud mill-karatteristiċi kaxxa li jappoġġjaw tipi ta 'ħtiġiet tan-negozju bħal dik.

B'mod ġenerali, one links two lists together using a lookup column. List A contains the invoice header information and list B contains invoice details.

Jużaw listi addizzjonali li jżommu klijent numri, numri tal-prodott, eċċ.

Uża parti kontenut tal-web query (fil MOSS biss) and/or a data view web part to create merged views of the lists. SQL Server Reporting Services (SRS) huwa wkoll disponibbli għall-naħa rappurtar ta 'dan.

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

• Daqs tal lookup relatati listi vs. "smartness" 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 oġġetti, that’s going to be a problem. The lookup control does not page through those items. Minflok, 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 "pull back" one column of information. You can never pull back more than one column of information from the source list. Per eżempju, you cannot select a customer "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. Stajt bil-miktub dwar dan hawn. You can’t implement cascading drop-downs, jippermettu kondizzjonalment / jiskonnettja oqsma, eċċ.
• 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. Per eżempju, SharePoint jippermettilek li toħloq żewġ listi tad-dwana, "customer" and "invoice header". You can create an invoice header that links back to a customer in the customer list. Imbagħad, you can delete the customer from the list. Barra mill-kaxxa, there is no way to prevent this. To solve this kind of problem, inti normalment tuża handlers avveniment.

Dan jista 'jidher skoraġġanti, 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 tgħinna biex timla dawn il-lakuni permezz ta 'għodod bħall-:

• Handlers Avveniment. Use them to enforce referential integrity.
• Kolonni Custom: Create custom column types and use them in lieu of the default lookup column. Add paging, buffering u l-karatteristiċi Ajax sabiex isiru sensittivi.
• 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 hija karatteristika MOSS (mhux disponibbli fil WSS) and is challenging to configure.

• Formola tal-web ASP.NET: Oħloq full-dehru forma AJAX-ppermettiet li juża l-mudell oġġett SharePoint u / jew servizzi tal-web għal-listi SharePoint lieva filwaqt li tipprovdi user interface ferm reattivi.

L-aħħar għażla tista 'tħossok bħal int tibda mill-bidu, iżda tikkunsidra l-fatt li l-pjattaforma SharePoint jibda inti off mal-karatteristiċi ewlenin li ġejjin:

• Sigurtà mudell ma 'manutenzjoni.
• Sistema menu mal-manutenzjoni.
• "Master table" (I.E. listi tad-dwana) mas-sigurtà, mibnija fil-manutenzjoni u l-verifika.
• Fittex.
• Back jispiċċaw integrazzjoni għodod (BDC).

Jekk tibda bi proġett blank ġdid fl-istudjo viżwali, ikollok ħafna ta 'infrastruttura u plumbing biex jibnu qabel ikollok qrib għal dak offerti 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, jekk jogħġbok leave kumment.

</aħħar>