Forum notendur oft og spurningum eins og þetta:

> Halló,
>
> Vinsamlegast segðu mér ef það eru einhverjar möguleikar til að byggja upp sérsniðna lista með
> skipstjóri og gerð upplýsinganna (eins reikningum) án þess að nota Infopath.
>

SharePoint afla sumir út af the kassi lögun sem styðja konar kröfur fyrirtækis eins og þessi.

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

Nota fleiri listum til að halda viðskiptavinar Reikningur, vörunúmerum, o.fl..

Notaðu fyrirspurn efni vefur hluti (í mosa aðeins) and/or a data view web part to create merged views of the lists. SQL Server Reporting Services (SRS) er einnig í boði fyrir skýrslugerð hlið hennar.

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

• Stærð tengdum útlit listum 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 atriði, that’s going to be a problem. The lookup control does not page through those items. Staðinn, 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. Til dæmis, 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. Ég hef skrifað um þetta hér. You can’t implement cascading drop-downs, skilyrðum virkja / slökkva reiti, o.fl..
• 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. Til dæmis, SharePoint leyfa þér að búa til tvær sérsniðnar lista, "customer" and "invoice header". You can create an invoice header that links back to a customer in the customer list. Þá, you can delete the customer from the list. Út af the kassi, there is no way to prevent this. To solve this kind of problem, þú myndir venjulega nota atburði dýraþjálfari.

Það kann að virðast hráslagalegur, 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 gerir okkur að fylla þær eyður nota tæki svo sem eins og:

• Event handlers. Use them to enforce referential integrity.
• Custom dálka: Create custom column types and use them in lieu of the default lookup column. Add paging, höggdeyfir og AJAX lögun til gera þá móttækilegur.
• 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 er MOSS lögun (ekki í boði í WSS) and is challenging to configure.

• ASP.NET vefform: Búa til fullur-lögun AJAX-virkt form sem notar SharePoint mótmæla líkan og / eða vefur þjónusta til að nýta SharePoint listi en að veita mjög móttækilegur notendaviðmót.

Síðasti valkostur getur finnst eins og þú ert að byrja frá grunni, en íhuga þá staðreynd að SharePoint vettvang byrjar þú burt með the hópur stuðningsmanna lykill lögun:

• Öryggi líkan með viðhald.
• Matseðill kerfi með viðhald.
• "Master table" (i.e. Raða listum) með öryggi, innbyggður-í viðhald og endurskoðun.
• Leita.
• Back End Integration verkfæri (BDC).

Ef þú byrjar með nýja auða verkefni í Visual Studio, þú hafa a einhver fjöldi af grunngerð og pípulagnir að byggja áður en þú nálgast það SharePoint býður.

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, vinsamlegast eftir athugasemd.

</enda>