Os usuarios do foro a miúdo como preguntas como esta:

> Ola,
>
> Por favor, me diga se hai posibilidades de construír unha lista personalizada con
> Tipo de mestre e de detalles (como facturas) sen usar InfoPath.
>

SharePoint ofrece algúns fóra das características da caixa que soportan tipos de requisitos de negocios coma este.

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

Usa as listas adicionais para manter o número de clientes, números de produtos, etc.

Usar a consulta de contidos web part (en só Moss) and/or a data view web part to create merged views of the lists. SQL Server Reporting Services (SRS) tamén está dispoñible para o lado da mesma comunicación.

Con todo, 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:

• Tamaño da investigación relacionada listas 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 items, that’s going to be a problem. The lookup control does not page through those items. Pola, 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. Por exemplo, 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. Eu escribín sobre iso aquí. You can’t implement cascading drop-downs, condicional activar / desactivar campos, etc.
• 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. Por exemplo, SharePoint permite que cree dúas listas personalizadas, "customer" and "invoice header". You can create an invoice header that links back to a customer in the customer list. Entón, you can delete the customer from the list. Fóra da caixa, there is no way to prevent this. To solve this kind of problem, usaría normalmente manipuladores de eventos.

Pode parecer sombrío, 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 permite cubrir esas lagoas usando ferramentas como:

• Event handlers. Use them to enforce referential integrity.
• Columnas personalizadas: Create custom column types and use them in lieu of the default lookup column. Add paging, buffer e os recursos AJAX para facelas sensibles.
• 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 é unha característica Moss (non está dispoñible no WSS) and is challenging to configure.

• Formulario web ASP.NET: Crear un formulario habilitados para AJAX completo que utiliza o modelo de obxecto do SharePoint e / ou servizos web para alavancar as listas do SharePoint, que proporciona unha interface de usuario moi sensible.

A última opción pode sentir como se está empezando de cero, pero considerar o feito de que a plataforma SharePoint comeza fóra coas seguintes características principais:

• Modelo de seguridade co mantemento.
• Sistema de menú co mantemento.
• "Master table" (i.e. Contraer personalizadas) con seguridade, built-in de mantemento e auditoría.
• Procurar.
• Volver acabar ferramentas de integración (BDC).

Se comeza cun novo proxecto en branco no visual studio, ten unha morea de infraestrutura e encanamento para construír antes de chegar preto do que o SharePoint ofrece.

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, por favor, deixe un comentario.

</final>