Kako bi zaobišli KPI problema Sam pisao o tome ovdje, I did some testing and discovered that KPI’s work against folders with meta data in the same way that they work against documents or list items. I proved it out by creating a new content type based on the folder content type and then added a few fields. I created some indicators and proved to myself that KPIs work as expected. This was welcome news. It’s not perfect, because the drill-down you get from the KPI against the folders is not exactly what you want. This isn’t too much a drawback in my case because 1) su krajnji korisnici ne znaju za bolje i 2) the drill-down goes to a folder. They click the folder name and they are at the item. It’s two clicks instead of one, što nije kraj svijeta.

This flowed nicely with the work I was doing. I am creating a folder for every document that gets uploaded. This is done via an event receiver. Kao rezultat toga, to je komad torte zadržati Roditelj mapom meta data in sync with the KPI-driven meta data from the file itself since the plumbing is already in place. This allows me to have my KPI’s and eat them too 🙂

I modified the event receiver to add the folder and then set this new folder’s content type to my custom KPI-friendly content type. This bit of code did the trick:

 SPFolderCollection srcFolders = targetWeb.GetFolder("Documents").Podmape;
  SPFolder addedFolder = srcFolders.Add(properties.ListItem.ID.ToString());

  SPContentTypeId kpiCT = novi SPContentTypeId("0x0120002A666CAA9176DC4AA8CBAA9DC6B4039F");
  addedFolder.Item["Content Type ID"] = KpiCT;
  addedFolder.Item.Update();

Da biste pronašli stvarni ID vrste sadržaja, Ja pogledana je vrsta sadržaja putem stranice postavki i copy / ga zalijepiti u URL kao što je prikazano:

</kraj>

Pretplatite se na moj blog!

Mrzim to priznati, but I struggled with this one all day. My event receiver needs to update a field of its parent folder. This little bit shows how to do it:

privatni poništiti UpdateParentFolder(SPItemEventProperties Svojstva)
{

SPFolder thisItemFolder = properties.ListItem.File.ParentFolder;
thisItemFolder.Item["ZZ Approval Status"] = "Good news, svako!";
thisItemFolder.Item.Update();


} // UpdateParentFolder

U tom slučaju, I’m working with a document library and the properties are coming from an ItemAdded event.

The trick is that you can’t get the SPFolder of the item directly from the item itself (i.e. properties.ListItem.Folder is null). Umjesto toga, go to the list item’s associated File and get the File’s folder.

</kraj>

Pretplatite se na moj blog!

I’m sure I’m not the first person to come up with this. Međutim, I haven’t noticed anyone publish a trick like this since I started paying close attention to the community last July. Tako, Mislio sam da bih objaviti ga to brzo i lako ispravljanje savjet.

I’m working on an event receiver that started to generate this error in the 12 košnica:

Pogreška pri učitavanju i trčanje događaj prijemnik Conchango.xyzzyEventReceiver u xyzzy, Verzija = 1.0.0.0, Kultura = neutralni, PublicKeyToken=blahbalhbalh. Additional information is below. : Objekta nije postavljena na instancu objekta.

I didn’t know where I had introduced this bug because I had done too many things in one of my code/deploy/test cycles.

I tried this solution to get my pdb in there with hopes that SharePoint’s 12 hive would show the stack trace, but no luck. I don’t know if it’s possible and if someone does, javite mi 🙂

I know it’s possible to write your own log messages to the 12 košnica. Frankly, I wanted something a little less scary and quicker to implement.

It occurred to me that I could at least get some basic trace information by catching and re-throwing generic exceptions like this:

  pokušati {
    UpdateEditionDate(Svojstva);
  }
  ulov (Izuzetak e)
  {
    baciti novi Izuzetak("Dispatcher, UpdateEditionDate(): Izuzetak: [" + e.ToString() + "].");
  }

This showed up in the 12 hive thusly:

Pogreška pri učitavanju i trčanje događaj prijemnik Conchango.xyzzyEventReceiver u xyzzy, Verzija = 1.0.0.0, Kultura = neutralni, PublicKeyToken=blahblahblah. Additional information is below. : Dispečer, UpdateEditionDate(): Izuzetak: [System.NullReferenceException: Objekta nije postavljena na instancu objekta. at Conchango.xyzzyManagementEventReceiver.UpdateEditionDate(SPItemEventProperties svojstva) at Conchango.xyzzyManagementEventReceiver.Dispatcher(SPItemEventProperties svojstva, String eventDescription)].

That gave me all the detail I needed to track down that particular problem and I expect to use it a lot going forward.

</kraj>

Pretplatite se na moj blog!

Ovaj prošli tjedan sam bio provedbi "razvija" solution for a client that uses BDC and SPQuery and ran into some difficulty using SPQuery against a document library containing folders. Bottom line: dodijeliti "rekurzivni" s pogledom na atribut upita.

Moj scenarij:

• U ponedjeljak,, Ću uploadati dokument i dostaviti neke meta podatke.
• Sljedeći tjedan, I upload a new document. Much of this new document’s meta data is based on the document I uploaded on Monday (which we call the "master document").
• Napravili smo fasadu web servis koji pruža BDC-friendly sučelje na popisu, tako da korisnici mogu jednostavno pronaći taj dokument ponedjeljak putem naslova pretraživanje.
• A BDC data column provides a friendly user interface. (To je dio mog pokušaja na korištenje BDC za više prijateljski Potraži stupac).

Konačna BDC fasada usluga koristi upita ovako raditi pretraživanja:

 // Koristi U2U alat za pomoć u stvaranju ovog CAML upit.
      oQuery.Query =
        "<Gdje>";

      ako (titleFilter.Length > 0)
        oQuery.Query   =
          "  <I>";

      oQuery.Query   =
        "    <I>" +
        "      <Geq>" +
        "        <FieldRef Name=\"DocumentId\" />" +
        "        <Value Type=\"Text\">" + minId + "</Vrijednost>" +
        "      </Geq>" +
        "      <Leq>" +
        "        <FieldRef Name=\"DocumentId\" />" +
        "        <Value Type=\"Text\">" + maxId + "</Vrijednost>" +
        "      </Leq>" +
        "    </I>";

      ako (titleFilter.Length > 0)
        oQuery.Query   =
          "    <Sadrži>" +
          "      <FieldRef Name=\"Title\" />" +
          "      <Value Type=\"Text\">" + titleFilter + "</Vrijednost>" +
          "    </Sadrži>" +
          "  </I>";
      oQuery.Query   =
        "</Gdje>";

U početnoj fazi razvoja, this worked great. Međutim, uveli smo mape u mapu za rješavanje nekih problema i odjednom, my BDC picker wouldn’t return any results. I tracked this down to the fact that the SPQuery would never return any results. We used folders primarily to allow multiple files with the same name to be uploaded but with different meta data. When the file is uploaded, smo izradili mapu na temelju popisa stavke ID, a zatim premjestiti datoteku postoji (O tome sam pisao ovdje; imali smo mješovite rezultate s ovim pristupom, ali u cjelini, to je rad i). The user don’t care about folders and in fact, don’t really understand that there are any folders. We have configured all the views on the library to show items without regard to folders.

I hit this problem twice as the technical implementation evolved and solved it differently each time. The first time, I wasn’t using the CONTAINS operator in the query. Without a CONTAINS operator, I was able to solve the problem by specifying the view on the SPQuery’s contructor. Instead of using the default constructor:

SPList oList = web.Lists["Documents"];

SPQuery oQuery = novi SPQuery();

I umjesto da se konstruktor koji navedenu pogled:

SPList oList = web.Lists["Documents"];

SPQuery oQuery = novi SPQuery(oList.Views["All Documents"]);

To je riješilo problem i počeo sam da se moje rezultate.

I then added the CONTAINS operator into the mix and it broke again. It turns out that the CONTAINS operator, koliko ja mogu reći, ne radi s pogledom na isti način kao jednostavniji geq / LEQ operators. I did some searching and learned that the query’s ViewAttributes should be set to "Recursive", kao u:

oQuery.ViewAttributes = "Scope=\"Recursive\"";

That solved the problem for CONTAINS. Zapravo, to također riješio moj izvorni pretragu problem i ako sam bio naveden rekurzivna značajke prvi put, Ne bih se izvoditi u pitanju opet.

Činjenica da je pogled na bazi SPQuery radi za neke operatere (Geq / Leq) a ne drugima (SADRŽI), zajedno s činjenicom da KPI ne čini uopće raditi s mape koje sadrže bibliotekama dokumenata vodi me da vjerujem da ima neke SPQuery ortogonalnost pitanja.

Posebne Hvala:

• Dobri ljudi u U2U i njihov upit alat.
• Michael Hoffer je super "učenje kroz rad" blog post, komentari i odgovori.

</kraj>

Pretplatite se na moj blog!

UPDATE 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. Sam opisao da je u malo više detalja ovdje.

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 (tehnikom slično onome što sam pisao o ovdje). 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" ali umjesto toga stvaraju dokumente na lokalnoj razini, a zatim ih prenijeti).

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".

To je obično jednostavan za napraviti i ja opisao nešto vrlo slično kao ovaj na SharePoint Beagle s puno zaslon metak ako vas zanima.

Ukratko, Ja sam sljedeće:

• Create a view on the doc library called "Pending".
• Konfiguracija pogled ignorirati strukturu mapa.
• Napravite popis ključnih pokazatelja uspješnosti.
• Create an indicator in the list that points to the doc lib and that "Pending" pogled.

This simply does not work. The KPI shows my target (e.g. pet hitnih dokumenti) but always shows the actual number of urgent documents as zero. Paradoxically, ako dođite do pojedinosti, 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".

Čini mi se da, iako ste odredili pogled, the KPI doesn’t honor the "show all items without folders" postavljanja i umjesto toga, ograničava na korijenske mape.

Ako sam u krivu, molimo ispadne mi linija ili komentiranje.

</kraj>

Pretplatite se na moj blog!