Upang gumawa sa paligid ng isang KPI problema Ko sinulat ni tungkol dito, 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) ang mga end user ay hindi alam ang anumang mas mahusay at 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, na kung saan ay hindi ang dulo ng mundo.

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. Bilang isang resulta, ito ay isang piraso ng keyk upang panatilihin ang mga parent folder ni 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").Subfolder;
  SPFolder Idinagdag folder = srcFolders.Add(properties.ListItem.ID.ToString());

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

Upang mahanap ang aktwal na Nilalaman Uri ng ID, I-access na uri ng nilalaman sa pamamagitan ng mga setting ng site at kopyahin / paste ito mula sa URL tulad ng ipinapakita:

</dulo>

Mag-subscribe sa aking blog!

Galit kong umamin ito, 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:

pribado walang bisa UpdateParentFolder(SPItemEventProperties katangian)
{

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


} // UpdateParentFolder

Sa kasong ito, Ako nagtatrabaho sa isang dokumento na library at ang mga katangian ay darating mula isang ItemAdded na kaganapan.

Ang lansihin ay na hindi mo makuha ang SPFolder ng item direkta mula sa item mismo (i.e. properties.ListItem.Folder ay null). Sa halip, pumunta sa nauugnay File ng mga item sa listahan at makakuha ng folder ang File.

</dulo>

Mag-subscribe sa aking blog!

I’m sure I’m not the first person to come up with this. Gayunman, I haven’t noticed anyone publish a trick like this since I started paying close attention to the community last July. Kaya, Naisip ko na gusto ko itong i-post ang mabilis at madaling tip debug.

Ako ay nagtatrabaho sa isang kaganapan na receiver na sinimulan upang bumuo ng ang error na ito sa 12 kaharian ng mga laywan:

Error sa paglo-load at tumatakbo kaganapan receiver Conchango.xyzzyEventReceiver sa xyzzy, Bersyon = 1.0.0.0, Culture = neutral, PublicKeyToken = blahbalhbalh. Additional information is below. : Object reference hindi nakatakda sa isang halimbawa ng isang bagay.

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.

Sinubukan kong ito solusyon upang makakuha ng aking pdb sa doon may pag-asa na SharePoint ni 12 kaharian ng mga laywan ay magpapakita ng mga stack trace, but no luck. I don’t know if it’s possible and if someone does, mangyaring ipaalam sa akin 🙂

Alam ko posible upang isulat ang iyong sariling mga mensahe log sa 12 kaharian ng mga laywan. Frankly, Nais kong isang bagay ng kaunti mas nakakatakot at mas mabilis na ipapatupad.

Ito ay naganap sa akin na maaari ko ng hindi bababa sa makakuha ng ilang mga pangunahing impormasyon sa pamamagitan ng trace pansing at muling ibinabato generic pagbubukod ganito:

  sumubok {
    UpdateEditionDate(katangian);
  }
  abutin (Kataliwasan at)
  {
    magtapon bago Kataliwasan("Dispatcher, UpdateEditionDate(): Kataliwasan: [" + e.ToString() + "].");
  }

Ito ay nagpakita ng hanggang sa ang 12 kaharian ng mga laywan thusly:

Error sa paglo-load at tumatakbo kaganapan receiver Conchango.xyzzyEventReceiver sa xyzzy, Bersyon = 1.0.0.0, Culture = neutral, PublicKeyToken = blahblahblah. Additional information is below. : Despatsador, UpdateEditionDate(): Kataliwasan: [System.NullReferenceException: Object reference hindi nakatakda sa isang halimbawa ng isang bagay. at Conchango.xyzzyManagementEventReceiver.UpdateEditionDate(SPItemEventProperties katangian) at Conchango.xyzzyManagementEventReceiver.Dispatcher(SPItemEventProperties katangian, String eventDescription)].

Na ibinigay mo sa akin ang lahat ng mga detalye na kailangan ko upang subaybayan ang down na partikular na problema at inaasahan kong gamitin ito ng maraming pasulong.

</dulo>

Mag-subscribe sa aking blog!

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. Ika-line: assign "recursive" sa view na katangian ng mga query.

Aking mga sitwasyong:

• Sa Monday, I-upload ang dokumento at matustusan ang ilang mga meta data.
• Ang mga sumusunod na linggo, 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").
• Lumikha kami ng isang web façade na serbisyo na nagbibigay ng isang BDC-friendly interface sa listahan upang ang mga user ay maaaring madaling mahanap na Lunes dokumento sa pamamagitan ng isang paghahanap pamagat.
• A BDC data column provides a friendly user interface. (Ito ay bahagi ng aking mga pagtatangka sa paggamit ng BDC para sa isang mas friendly na hanay ng Paghahanap).

Ang huling BDC façade serbisyo ay gumagamit ng isang query tulad nito upang gawin ang paghahanap:

 // Ginamit U2U tool upang makatulong sa pagbuo ng mga ito CAML query.
      oQuery.Query =
        "<Saan>";

      kung (titleFilter.Length > 0)
        oQuery.Query   =
          "  <At>";

      oQuery.Query   =
        "    <At>" +
        "      <Geq>" +
        "        <FieldRef Name=\"DocumentId\" />" +
        "        <Value Type=\"Text\">" + MinID + "</Halaga>" +
        "      </Geq>" +
        "      <Leq>" +
        "        <FieldRef Name=\"DocumentId\" />" +
        "        <Value Type=\"Text\">" + maxId + "</Halaga>" +
        "      </Leq>" +
        "    </At>";

      kung (titleFilter.Length > 0)
        oQuery.Query   =
          "    <Naglalaman ng>" +
          "      <FieldRef Name=\"Title\" />" +
          "      <Value Type=\"Text\">" + titleFilter + "</Halaga>" +
          "    </Naglalaman ng>" +
          "  </At>";
      oQuery.Query   =
        "</Saan>";

Sa panahon ng unang yugto ng pag-unlad, this worked great. Gayunman, ipinakilala namin ang mga folder sa direktoryo upang malutas ang ilang mga problema at bigla, 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, lumikha kami ng isang folder batay sa mga ID ng mga item sa listahan at pagkatapos ay ilipat ang mga file doon (Ko sinulat ni tungkol sa na dito; mayroon kaming halo-halong mga resulta may diskarteng ito ngunit sa kabuuan, ito ay mahusay na gumagana). 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 = bago SPQuery();

Ko sa halip ay gumamit ng isang constructor na tinukoy ng tanawin:

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

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

Na malulutas ang problema ko at sinimulan upang makakuha ng aking mga resulta.

I then added the CONTAINS operator into the mix and it broke again. It turns out that the CONTAINS operator, sa ngayon bilang ang maaari kong sabihin, ay hindi gumagana sa view ng ang parehong paraan tulad ng isang mas simpleng GEQ / LEQ operators. I did some searching and learned that the query’s ViewAttributes should be set to "Recursive", tulad ng sa:

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

That solved the problem for CONTAINS. Sa katunayan, ito rin malutas sa aking orihinal na problema sa paghahanap at kung ako ay tinukoy ang recursive katangian sa unang pagkakataon, Hindi ko nais na tumakbo sa mga isyu muli.

Ang katotohanan na ang isang pagtingin na batay sa SPQuery gumagana para sa ilang mga operator (GEQ/LEQ) at hindi ang iba (NAGLALAMAN), isinama sa ang katunayan na ang KPI hindi mukhang gumana sa lahat ng mga may-folder na naglalaman ng mga library dokumento humantong sa akin upang maniwala na SPQuery ay may ilang mga isyu orthogonality.

Espesyal na Salamat:

• Ang mabuting tao sa U2U at ang kanilang mga query tool.
• Michael Hoffer ni dakilang "pag-aaral sa pamamagitan ng paggawa" blog post, mga komento at mga tugon.

</dulo>

Mag-subscribe sa aking blog!

I-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 dito). 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 with lots of screen shots if you’re interested.

In a nutshell, I did the following:

• Create a view on the doc library called "Pending".
• Configure the view to ignore folder structure.
• Create a KPI List.
• Create an indicator in the list that points to the doc lib and that "Pending" tingnan.

This simply does not work. The KPI shows my target (e.g. five urgent documents) but always shows the actual number of urgent documents as zero. Paradoxically, if you drill down to the details, 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".

Lumilitaw sa akin na kahit na iyong tinukoy ng tanawin, the KPI doesn’t honor the "show all items without folders" pagtatakda at sa halip ay, paligid mismo sa folder na root.

Kung ako ay mali, mangyaring i-drop ako ng isang linya o mag-iwan ng komento.

</dulo>

Mag-subscribe sa aking blog!