Í því skyni að vinna í kringum KPI vandamál Ég skrifaði um hér, 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) the endir notandi veit ekki betur og 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, sem er ekki the endir af the heiminum.

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. Þar af leiðandi, það er a stykki af köku til að halda foreldri mappa er meta data in sync with the KPI-driven meta data from the file itself since the plumbing is already in place. Þetta gerir mér kleift að hafa KPI og borða þau líka 🙂

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").Undirmöppur;
  SPFolder við möppu = srcFolders.Add(properties.ListItem.ID.ToString());

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

Til að finna raunverulegt innihald Auðkenni, Ég nálgast þessi efni gerð í gegnum stillingar á síðuna og afrita / líma það frá vefslóð eins og sýnt:

</enda>

Gerast áskrifandi að bloggið mitt!

Ég hata að viðurkenna það, 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:

einkaaðila ógilt UpdateParentFolder(SPItemEventProperties eignir)
{

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


} // UpdateParentFolder

Í þessu tilviki, Ég er að vinna með skjal bókasafn og eignir eru að koma frá ItemAdded atburði.

The bragð er að þú getur ekki fengið SPFolder hlutarins beint frá hlutnum sjálfum (i.e. properties.ListItem.Folder er null). Staðinn, fara tengslum skrá á lista yfir atriði og fá möppu Skráin er.

</enda>

Gerast áskrifandi að bloggið mitt!

I’m sure I’m not the first person to come up with this. Hins, I haven’t noticed anyone publish a trick like this since I started paying close attention to the community last July. Svo, Ég hélt ég myndi eftir það þetta fljótleg og auðveld kemba þjórfé.

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

Villa hleðsla og gangi móttakari Conchango.xyzzyEventReceiver í xyzzy, Útgáfa = 1.0.0.0, Menning = hlutlaus, PublicKeyToken=blahbalhbalh. Additional information is below. : Object tilvísun ekki sett til dæmis á hlut.

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, please let me know 🙂

I know it’s possible to write your own log messages to the 12 Hive. 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:

  reyna {
    UpdateEditionDate(eignir);
  }
  veiða (Undantekning e)
  {
    kasta ný Undantekning("Dispatcher, UpdateEditionDate(): Undantekning: [" + e.ToString() + "].");
  }

This showed up in the 12 hive thusly:

Villa hleðsla og gangi móttakari Conchango.xyzzyEventReceiver í xyzzy, Útgáfa = 1.0.0.0, Menning = hlutlaus, PublicKeyToken=blahblahblah. Additional information is below. : Dispatcher, UpdateEditionDate(): Undantekning: [System.NullReferenceException: Object tilvísun ekki sett til dæmis á hlut. at Conchango.xyzzyManagementEventReceiver.UpdateEditionDate(SPItemEventProperties eignir) at Conchango.xyzzyManagementEventReceiver.Dispatcher(SPItemEventProperties eignir, 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.

</enda>

Gerast áskrifandi að bloggið mitt!

This past week I was implementing an "evolving" solution for a client that uses BDC and SPQuery and ran into some difficulty using SPQuery against a document library containing folders. Neðsta lína: assign "recursive" að skoða eiginleiki af fyrirspurninni.

Atburðarás minn:

• Á mánudaginn, Ég hlaða skjal og veita sumir meta gögn.
• The following week, 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").
• We’ve created a web service façade that provides a BDC-friendly interface to the list so that users can easily locate that Monday document via a title search.
• A BDC data column provides a friendly user interface. (This is part of my attempt at using BDC for a more friendly Lookup column).

The final BDC façade service uses a query like this to do the lookup:

 // Used U2U tool to assist in generating this CAML query.
      oQuery.Query =
        "<Hvar>";

      ef (titleFilter.Length > 0)
        oQuery.Query  =
          "  <Og>";

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

      ef (titleFilter.Length > 0)
        oQuery.Query  =
          "    <Inniheldur>" +
          "      <FieldRef Name=\"Title\" />" +
          "      <Value Type=\"Text\">" + titleFilter + "</Gildi>" +
          "    </Inniheldur>" +
          "  </Og>";
      oQuery.Query  =
        "</Hvar>";

During the initial stage of development, this worked great. Hins, we introduced folders into the directory to solve some problems and suddenly, 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, we create a folder based on the list item’s ID and then move the file there (I wrote about that hér; we’ve had mixed results with this approach but on the whole, it’s working well). 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 = ný SPQuery();

I instead used a constructor that specified a view:

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

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

That solved the problem and I started to get my results.

I then added the CONTAINS operator into the mix and it broke again. It turns out that the CONTAINS operator, so far as I can tell, does not work with the view the same way as the a simpler GEQ / LEQ operators. I did some searching and learned that the query’s ViewAttributes should be set to "Recursive", eins og í:

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

That solved the problem for CONTAINS. Í raun, þetta leyst einnig upprunalega leita vandamál mitt og ef ég hefði tilgreint endurkvæma eiginleiki í fyrsta sinn, Ég myndi ekki hafa keyrt inn í málið aftur.

Sú staðreynd að skoða byggir SPQuery virkar fyrir suma rekstraraðila (GEQ / LEQ) og ekki aðra (Inniheldur), ásamt þeirri staðreynd að KPIs virðist ekki vinna á öllum með möppu innihalda skjal bókasöfnum leiðir mig að trúa því að SPQuery hefur sumir orthogonality málefni.

Sérstakar þakkir:

• Góðu fólkinu á U2U og fyrirspurn tól þeirra.
• Michael Hoffer mikill "læra með því að gera" blogg, athugasemdir og viðbrögð.

</enda>

Gerast áskrifandi að bloggið mitt!

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. I described that in a little more detail here.

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 (using a technique similar to what I wrote about hér). 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" but instead create the docs locally and then upload them).

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

This is usually simple to do and I described something very much like this at the SharePoint Beagle með fullt af skjámyndum ef þú hefur áhuga.

Í stuttu máli, Ég gerði eftirfarandi:

• Create a view on the doc library called "Pending".
• Stilltu útsýnið til að hunsa möppuskipulag.
• Búðu til KPI lista.
• Create an indicator in the list that points to the doc lib and that "Pending" skoða.

Þetta einfaldlega gengur ekki. KPI sýnir markmiðið mitt (e.g. fimm brýn skjöl) en sýnir alltaf raunverulegan fjölda brýnna skjala sem núll. Þversagnakennt, ef þú kafar niður í smáatriðin, það sýnir fimm brýn skjöl á listanum. Ég bjó til mjög einfalda atburðarás með tveimur skjölum, einn í möppu og einn ekki. 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".

It appears to me that even though you specify a view, the KPI doesn’t honor the "show all items without folders" setting and instead, confines itself to the root folder.

If I’m wrong, please drop me a line or leave a comment.

</enda>

Gerast áskrifandi að bloggið mitt!