In order to work around a KPI problem I wrote about here, 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 end users don’t know any better and 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. Kama matokeo, 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. Hii inaruhusu yangu kuwa wangu KPI na kula nao pia 🙂

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;
  SPFolder addedFolder = srcFolders.Add(properties.ListItem.ID.ToString());

  SPContentTypeId kpiCT = mpya 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:

</mwisho>

Kujiunga na blog yangu!

I hate kukubali hilo, 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:

binafsi utupu UpdateParentFolder(SPItemEventProperties mali)
{

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


} // UpdateParentFolder

Katika kesi hiyo, Mimi nina kazi na maktaba hati na mali ni kuja kutoka tukio ItemAdded.

hila ni kwamba huwezi kupata SPFolder ya bidhaa moja kwa moja kutoka bidhaa yenyewe (i.e. properties.ListItem.Folder ni null). Badala yake, kwenda Picha bidhaa orodha ya kuhusishwa na kupata folder faili ya.

</mwisho>

Kujiunga na blog yangu!

I’m sure I’m not the first person to come up with this. Hata hivyo, I haven’t noticed anyone publish a trick like this since I started paying close attention to the community last July. Hivyo, Nilidhani ningependa baada ya kuwa hii haraka na rahisi Debug ncha.

Mimi nina kazi ya receiver tukio hilo kuwa ilianza kuzalisha kosa hili katika 12 mzinga:

Hitilafu ya upakiaji na mbio tukio receiver Conchango.xyzzyEventReceiver katika xyzzy, Version = 1.0.0.0, Utamaduni = neutral, PublicKeyToken = blahbalhbalh. Additional information is below. : Kitu kumbukumbu si kuweka mfano wa kitu.

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.

Nilijaribu ufumbuzi huu kupata PDB yangu katika huko pamoja na matumaini kwamba SharePoint ya 12 mzinga bila kuonyesha mpororo, but no luck. I don’t know if it’s possible and if someone does, tafadhali napenda kujua 🙂

Najua inawezekana kuandika ujumbe yako mwenyewe logi kwa 12 mzinga. Frankly, Nilitaka kitu kidogo kidogo inatisha na wepesi kutekeleza.

Ilitokea kwangu kwamba mimi naweza angalau kupata baadhi ya msingi kuwaeleza habari na kuambukizwa na re-kutupa isipokuwa generic kama hii:

  kujaribu {
    UpdateEditionDate(mali);
  }
  kukamata (Ubaguzi e)
  {
    kutupa mpya Ubaguzi("Dispatcher, UpdateEditionDate(): Ubaguzi: [" + e.ToString() + "].");
  }

Hii ilionyesha juu katika 12 mzinga thusly:

Hitilafu ya upakiaji na mbio tukio receiver Conchango.xyzzyEventReceiver katika xyzzy, Version = 1.0.0.0, Utamaduni = neutral, PublicKeyToken = blahblahblah. Additional information is below. : Dispatcher, UpdateEditionDate(): Ubaguzi: [System.NullReferenceException: Kitu kumbukumbu si kuweka mfano wa kitu. at Conchango.xyzzyManagementEventReceiver.UpdateEditionDate(SPItemEventProperties mali) at Conchango.xyzzyManagementEventReceiver.Dispatcher(SPItemEventProperties mali, Kamba eventDescription)].

Kwamba alinipa undani wote mimi zinahitajika kufuatilia kwamba tatizo fulani na mimi kutarajia matumizi yake mengi kwenda mbele.

</mwisho>

Kujiunga na blog yangu!

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. Bottom line: assign "recursive" kwa sifa mtazamo wa swala.

Yangu mazingira:

• Jumatatu, Mimi upload hati na ugavi baadhi ya data meta.
• Wiki iliyofuata, 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").
• Tumeunda huduma ya mtandao façade ambayo hutoa interface BDC-kirafiki na orodha hivyo kwamba watumiaji urahisi Machapisho kwamba hati Jumatatu kupitia tafuta cheo.
• A BDC data column provides a friendly user interface. (Hii ni sehemu ya jaribio yangu katika kutumia BDC kwa safu zaidi ya kirafiki Lookup).

mwisho BDC façade huduma anatumia swala kama hii kufanya lookup:

 // Kutumika U2U chombo ili kusaidia katika kuzalisha hii hoja CAML.
      oQuery.Query =
        "<Ambapo>";

      kama (titleFilter.Length > 0)
        oQuery.Query   =
          "  <Na>";

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

      kama (titleFilter.Length > 0)
        oQuery.Query   =
          "    <Ina>" +
          "      <FieldRef Name=\"Title\" />" +
          "      <Value Type=\"Text\">" + titleFilter + "</Thamani>" +
          "    </Ina>" +
          "  </Na>";
      oQuery.Query   =
        "</Ambapo>";

Wakati wa hatua ya awali ya maendeleo, this worked great. Hata hivyo, sisi ilianzisha folders katika saraka ya kutatua baadhi ya matatizo na ghafla, 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, sisi kujenga folder msingi ID bidhaa orodha na kisha kuondoka faili huko (Niliandika kuhusu kwamba hapa; tulikuwa na mchanganyiko matokeo na mfumo huu lakini kwa ujumla, ni kazi vizuri). 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 = mpya SPQuery();

Mimi badala kutumika kuujenga kwamba maalum mtazamo:

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

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

Kwamba kutatuliwa tatizo na mimi kuanza kupata matokeo yangu.

I then added the CONTAINS operator into the mix and it broke again. It turns out that the CONTAINS operator, hivyo mbali kama naweza kuwaambia, haifanyi kazi kwa lengo njia ile ile kama GEQ rahisi / LEQ operators. I did some searching and learned that the query’s ViewAttributes should be set to "Recursive", kama katika:

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

That solved the problem for CONTAINS. Kwa kweli, hii pia kutatuliwa tafuta yangu ya awali tatizo na kama alikuwa maalum sifa kujirudia mara ya kwanza, Mimi bila kuwa na kukimbia katika suala tena.

ukweli kwamba SPQuery maoni makao kazi kwa waendeshaji baadhi (GEQ/LEQ) na si watu wengine (Ina), pamoja na ukweli kwamba KPIs hawaonekani kazi wakati wote na maktaba hati folder zenye inaongoza mimi kuamini kwamba SPQuery ina baadhi ya masuala orthogonality.

Shukrani maalum:

• folks mzuri katika U2U na chombo yao swala.
• Michael Hoffer kubwa "kujifunza kwa kutenda" blog post, maoni na majibu.

</mwisho>

Kujiunga na blog yangu!

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. Mimi alielezea kwamba katika undani zaidi kidogo hapa.

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 (kutumia mbinu sawa na kile aliandika kuhusu hapa). 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" lakini badala yake kuunda maandiko ndani ya nchi na kisha kuzipeleka).

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

Hii ni kawaida rahisi kufanya na mimi ilivyoelezwa kitu sana kama hii ifikapo Beagle SharePoint kwa kura ya screen shots kama wewe ni nia ya.

Kwa kifupi, Nilifanya zifuatazo:

• Create a view on the doc library called "Pending".
• Configure maoni kupuuza folder muundo.
• Kujenga Orodha KPI.
• Create an indicator in the list that points to the doc lib and that "Pending" mtazamo.

This simply does not work. The KPI shows my target (e.g. tano ya haraka nyaraka) but always shows the actual number of urgent documents as zero. Paradoxically, kama wewe kuchimba chini kwa maelezo, 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".

Inaonekana kwangu kwamba hata kama wewe bayana mtazamo, the KPI doesn’t honor the "show all items without folders" kuweka na badala yake, mipaka yenyewe ya folder mzizi.

Kama mimi nina makosa, tafadhali tone mimi line au kuacha maoni.

</mwisho>

Kujiunga na blog yangu!