אין סדר צו אַרבעטן אַרום אַ קפּי פּראָבלעם איך געשריבן וועגן דאָ, 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) דער סוף ניצערס טאָן נישט וויסן קיין בעסער און 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, which isn’t the end of the world.

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. ווי אַ רעזולטאַט, it’s a piece of cake to keep the parent folder’s meta data in sync with the KPI-driven meta data from the file itself since the plumbing is already in place. דאָס אַלאַוז מיר צו האָבן מיין קפּי ס און זיי אויך עסן 🙂

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").SubFolders;
  ספּפאָלדער addedFolder = srcFolders.Add(properties.ListItem.ID.ToString());

  SPContentTypeId kpiCT = נייַ SPContentTypeId("0x0120002A666CAA9176DC4AA8CBAA9DC6B4039F");
  addedFolder.Item["Content Type ID"] = kpiCT;
  addedFolder.Item.Update();

To locate the actual Content Type ID, I accessed that content type via site settings and copy/pasted it from the URL as shown:

</עק>

אַבאָנירן צו מיין בלאָג!

איך האַס צו אַרייַנלאָזן עס, 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:

פּריוואַט פּאָסל ופּדאַטעפּאַרענטפאָלדער(ספּיטעמעווענטפּראָפּערטיעס פּראָפּערטיעס)
{

ספּפאָלדער thisItemFolder = properties.ListItem.File.ParentFolder;
טהיסיטעמפאָלדער.יטעם["ZZ Approval Status"] = "Good news, יעדער יינער!";
טהיסיטעמפאָלדער.יטעמ.ופּדאַטע();


} // ופּדאַטעפּאַרענטפאָלדער

אין דעם פאַל, 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 (י.ע. properties.ListItem.Folder is null). אַנשטאָט, go to the list item’s associated File and get the File’s folder.

</עק>

אַבאָנירן צו מיין בלאָג!

I’m sure I’m not the first person to come up with this. אָבער, I haven’t noticed anyone publish a trick like this since I started paying close attention to the community last July. אַזוי, איך געדאַנק איך 'ד פּאָסטן עס דעם שנעל און גרינג דיבאַג שפּיץ.

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

טעות Loading און פליסנדיק געשעעניש ופנעמער קאָנטשאַנגאָ.קסיזזיעווענטרעסעיווער אין קסיזזי, ווערסיע = 1.0.0.0, קולטור = נייטראַל, PublicKeyToken=blahbalhbalh. Additional information is below. : כייפעץ דערמאָנען נישט שטעלן צו אַ בייַשפּיל פון אַ כייפעץ.

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 כייוו. Frankly, I wanted something a little less scary and quicker to implement.

עס פארגעקומען צו מיר אַז איך קען לפּחות באַקומען עטלעכע גרונט שפּור אינפֿאָרמאַציע דורך קאַטשינג און שייַעך-פארווארפן דזשאַנעריק אויסנעמען ווי דעם:

  פּרובירן {
    ופּדאַטעעדיטיאָנדאַטע(פּראָפּערטיעס);
  }
  כאַפּן (ויסנעם און)
  {
    וואַרפן נייַ ויסנעם("Dispatcher, ופּדאַטעעדיטיאָנדאַטע(): ויסנעם: [" + ע.טאָסטרינג() + "].");
  }

דאס אנטפלעקט זיך אין די 12 כייוו דאַסלי:

טעות Loading און פליסנדיק געשעעניש ופנעמער קאָנטשאַנגאָ.קסיזזיעווענטרעסעיווער אין קסיזזי, ווערסיע = 1.0.0.0, קולטור = נייטראַל, פּובליקקייטאָקען = בלאַהבלאַהבלאַה. Additional information is below. : דיספּאַטטשער, ופּדאַטעעדיטיאָנדאַטע(): ויסנעם: [סיסטעמ.נוללרעפערענסעעקססעפּטיאָן: כייפעץ דערמאָנען נישט שטעלן צו אַ בייַשפּיל פון אַ כייפעץ. at Conchango.xyzzyManagementEventReceiver.UpdateEditionDate(ספּיטעמעווענטפּראָפּערטיעס פּראָפּערטיעס) at Conchango.xyzzyManagementEventReceiver.Dispatcher(ספּיטעמעווענטפּראָפּערטיעס פּראָפּערטיעס, שטריקל עווענטדעסקריפּטיאָן)].

וואָס האט מיר אַלע די דעטאַל איך דארף צו שפּור אַראָפּ אַז באַזונדער פּראָבלעם און איך דערוואַרטן צו נוצן עס אַ פּלאַץ געגאנגען פאָרויס.

</עק>

אַבאָנירן צו מיין בלאָג!

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. דנאָ שורה: assign "recursive" to the view attribute of the query.

My scenario:

• On Monday, I upload a document and supply some meta data.
• 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 =
        "<ווו>";

      צי (titleFilter.Length > 0)
        oQuery.Query  =
          "  <און>";

      oQuery.Query  =
        "    <און>" +
        "      <Geq>" +
        "        <FieldRef Name=\"DocumentId\" />" +
        "        <Value Type=\"Text\">" + minId + "</ווערט>" +
        "      </Geq>" +
        "      <Leq>" +
        "        <FieldRef Name=\"DocumentId\" />" +
        "        <Value Type=\"Text\">" + maxId + "</ווערט>" +
        "      </Leq>" +
        "    </און>";

      צי (titleFilter.Length > 0)
        oQuery.Query  =
          "    <כּולל>" +
          "      <FieldRef Name=\"Title\" />" +
          "      <Value Type=\"Text\">" + titleFilter + "</ווערט>" +
          "    </כּולל>" +
          "  </און>";
      oQuery.Query  =
        "</ווו>";

During the initial stage of development, this worked great. אָבער, 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 דאָ; 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:

ספּליסט oList = web.Lists["Documents"];

SPQuery oQuery = נייַ SPQuery();

I instead used a constructor that specified a view:

ספּליסט oList = web.Lists["Documents"];

SPQuery oQuery = נייַ 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", ווי אין:

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

That solved the problem for CONTAINS. אין פאַקט, this also solved my original search problem and if I had specified the recursive attribute the first time, I would not have run into the issue again.

The fact that a view-based SPQuery works for some operators (GEQ/LEQ) and not others (CONTAINS), coupled with the fact that KPIs don’t seem to work at all with folder-containing document libraries leads me to believe that SPQuery has some orthogonality issues.

Special Thanks:

• The good folks at U2U and their query tool.
• Michael Hoffer’s great "learning by doing" בלאָג פּאָסטן, comments and responses.

</עק>

אַבאָנירן צו מיין בלאָג!

דערהייַנטיקן 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. איך דיסקרייבד אַז אין אַ קליין מער דעטאַל דאָ.

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 (ניצן אַ טעכניק ענלעך צו וואָס איך געשריבן וועגן דאָ). 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" אָבער אַנשטאָט מאַכן די דאָקס לאָוקאַלי און דעמאָלט צופֿעליקער זיי).

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

דאס איז יוזשאַוואַלי פּשוט צו טאָן און איך דיסקרייבד עפּעס זייער פיל ווי דאָס בייַ די שאַרעפּאָינט בעאַגלע מיט גורל פון פאַרשטעלן שאַץ אויב איר ניטאָ אינטערעסירט.

אין אַ נאַטשעל, איך האט די פאלגענדע:

• Create a view on the doc library called "Pending".
• קאַנפיגיער די מיינונג צו איגנאָרירן טעקע סטרוקטור.
• שאַפֿן אַ קפּי רשימה.
• Create an indicator in the list that points to the doc lib and that "Pending" מיינונג.

This simply does not work. The KPI shows my target (e.g. פינף דרינגלעך דאָקומענטן) but always shows the actual number of urgent documents as zero. Paradoxically, אויב איר בויער אַראָפּ צו די פרטים, 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".

עס אויס צו מיר אַז אַפֿילו כאָטש איר ספּעציפיצירן אַ מיינונג, the KPI doesn’t honor the "show all items without folders" באַשטעטיקן און אַנשטאָט, קאַנפיינז זיך צו דער וואָרצל טעקע.

אויב איך בין אומרעכט, ביטע פאַלן מיר אַ שורה אָדער לאָזן אַ באַמערקונג.

</עק>

אַבאָנירן צו מיין בלאָג!