Actualización 02/29/08: I solved this problem by creating a folder and then assigning a content type to the folder which has the meta data I need for the KPIs. Eu describe que un pouco máis de detalles aquí.
We have implemented a technical solution where users upload documents to a document library. An event receiver creates a directory and moves the file to that directory (usando unha técnica similar ao que escribín sobre aquí). We’ve successfully navigated around the potential issues caused by event receivers that rename uploaded files (mainly because users never start their document by clicking on "New" mais en vez diso crear os documentos localmente e despois envialos).
The meta data for these documents includes a Yes/No site column called "Urgent" and another site column called "Status". We need to meet a business requirement that shows the percentage of "Urgent" documents whose status is "Pending".
Xeralmente isto é simple e eu describe algo moi parecido a isto no Beagle SharePoint con moitas capturas de pantalla se vostede está interesado.
En poucas palabras, Eu fixen o seguinte:
- Create a view on the doc library called "Pending".
- Configure o punto de vista de ignorar estructura de cartafoles.
- Crear unha lista de KPI.
- Create an indicator in the list that points to the doc lib and that "Pending" ver.
This simply does not work. The KPI shows my target (e.g. cinco documentos urxentes) but always shows the actual number of urgent documents as zero. Paradoxically, afondar nos detalles, it shows the five urgent documents in the list. I created a very simple scenario with two documents, one in a folder and one not. Here is the screen shot:
The above screen shot clearly shows there are two documents in the view but the "value" is one. The "CamlSchema" with blank document Id is in the root folder and the other is in a folder named "84".
Paréceme que aínda que especifique unha visión, the KPI doesn’t honor the "show all items without folders" fixación e, no canto, Limítase a cartafol raíz.
Se eu está mal, por favor mande-me unha liña ou deixar un comentario.
</final>
John Ross