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. Bħala riżultat, 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. 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").SubFolders;
  SPFolder addedFolder = srcFolders.Add(properties.ListItem.ID.ToString());

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

</aħħar>

Abbona għall-blog tiegħi!

Ddejjaqni li jammettu li, 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:

privat null UpdateParentFolder(SPItemEventProperties proprjetajiet)
{

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


} // UpdateParentFolder

F'dan il-każ, Jien jaħdmu ma 'librerija dokument u l-proprjetajiet huma ġejjin minn avveniment ItemAdded.

Il-trick huwa li inti ma tistax tikseb l-SPFolder 'l-oġġett direttament mill-oġġett innifsu (I.E. properties.ListItem.Folder huwa null). Minflok, mur File assoċjati l-oġġett lista u jiksbu folder tal-fajl.

</aħħar>

Abbona għall-blog tiegħi!

I’m sure I’m not the first person to come up with this. Madankollu, I haven’t noticed anyone publish a trick like this since I started paying close attention to the community last July. Allura, Ħsibt I d jimpustah dan il-ponta debug malajr u faċli.

Jien jaħdmu fuq riċevitur każ li bdew jiġġeneraw dan l-iżball fil- 12 doqqajs:

Jtellgħu u jħaddmu Żball avveniment riċevitur Conchango.xyzzyEventReceiver fil xyzzy, Verżjoni = 1.0.0.0, Kultura = newtrali, PublicKeyToken = blahbalhbalh. Additional information is below. : Referenza Għan mhux stabbiliti għal istanza ta 'oġġett.

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 ppruvaw din is-soluzzjoni tikseb PDB tiegħi fil hemm ma 'jittama li l-SharePoint 12 doqqajs kieku juru t traċċa munzell, iżda l-ebda xortih. I don’t know if it’s possible and if someone does, jekk jogħġbok let me know 🙂

Naf huwa possibbli li jiktbu messaġġi tiegħek log stess għall- 12 doqqajs. Frankly, I riedu xi ftit inqas scary u aktar malajr biex jimplimentaw.

Dan ġara lili li I jistgħu għall-inqas nikseb xi traċċa informazzjoni bażika mill-qbid u mill-ġdid jitfg eċċezzjonijiet ġeneriċi bħal dan:

  jippruvaw {
    UpdateEditionDate(proprjetajiet);
  }
  qabda (Eċċezzjoni u)
  {
    tarmi ġdid Eċċezzjoni("Dispatcher, UpdateEditionDate(): Eċċezzjoni: [" + e.ToString() + "].");
  }

Dan wera up fil- 12 doqqajs thusly:

Jtellgħu u jħaddmu Żball avveniment riċevitur Conchango.xyzzyEventReceiver fil xyzzy, Verżjoni = 1.0.0.0, Kultura = newtrali, PublicKeyToken = blahblahblah. Additional information is below. : Dispatcher, UpdateEditionDate(): Eċċezzjoni: [System.NullReferenceException: Referenza Għan mhux stabbiliti għal istanza ta 'oġġett. at Conchango.xyzzyManagementEventReceiver.UpdateEditionDate(Proprjetajiet SPItemEventProperties) at Conchango.xyzzyManagementEventReceiver.Dispatcher(Proprjetajiet SPItemEventProperties, EventDescription String)].

Li tatni l-dettall I meħtieġa biex jillokalizzaw din il-problema partikolari u nistenna li jużawh ħafna miexi 'l quddiem.

</aħħar>

Abbona għall-blog tiegħi!

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" għall-attribut dawl tal-mistoqsija.

Xenarju tiegħi:

• Nhar it-Tnejn, I ittella 'dokument u jissupplixxi xi metadata.
• Il-ġimgħa li ġejja, 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").
• Imxejna ħolqot faċċata servizz web li jipprovdi interface BDC-friendly mal-lista sabiex l-utenti jistgħu faċilment jillokalizza dak id-dokument it-Tnejn permezz ta 'tfittxija titolu.
• A BDC data column provides a friendly user interface. (Din hija parti mill tentattiv tiegħi fl-użu BDC għal kolonna Lookup aktar faċli).

Il-finali BDC servizz façade juża mistoqsija bħal din tagħmel l-Lookup:

 // Użati għodda U2U biex jgħinu fil-ġenerazzjoni din il-mistoqsija CAML.
      oQuery.Query =
        "<Fejn>";

      jekk (titleFilter.Length > 0)
        oQuery.Query   =
          "  <U>";

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

      jekk (titleFilter.Length > 0)
        oQuery.Query   =
          "    <Fih>" +
          "      <FieldRef Name=\"Title\" />" +
          "      <Value Type=\"Text\">" + titleFilter + "</Valur>" +
          "    </Fih>" +
          "  </U>";
      oQuery.Query   =
        "</Fejn>";

Matul l-istadju inizjali ta 'żvilupp, this worked great. Madankollu, aħna introduċiet folders fil-direttorju biex isolvu xi problemi u f'daqqa waħda, 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, aħna toħloq folder bbażata fuq ID-oġġett lista u mbagħad jimxu l-fajl hemmhekk (I kiteb dwar dan hawn; aħna kellna riżultati mħallta ma dan l-approċċ, iżda fuq kollox, huwa xogħol tajjeb). 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 = ġdid SPQuery();

I minflok jintuża kostruttur dik speċifikata ħsieb:

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

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

Li tissolva l-problema u I bdiet tikseb riżultati tiegħi.

I then added the CONTAINS operator into the mix and it broke again. It turns out that the CONTAINS operator, safejn peux, ma taħdem ma 'l-opinjoni l-istess mod bħall-a GEQ sempliċi / LEQ operators. I did some searching and learned that the query’s ViewAttributes should be set to "Recursive", kif fil-:

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

That solved the problem for CONTAINS. Fil-fatt, dan solvuti wkoll problema tiegħi tfittxija oriġinali u jekk kelli speċifikat l-attribut jirrikorri l-ewwel darba, I ma kien ikun imur lejn il-kwistjoni mill-ġdid.

Il-fatt li SPQuery bbażata view xogħlijiet għal ċerti operaturi (GEQ/LEQ) u mhux oħrajn (FIH), flimkien mal-fatt li KPIs ma jidhirx li jaħdmu fil-livelli kollha mal-libreriji li fihom folder dokument twassalni biex jemmnu li SPQuery għandha xi kwistjonijiet orthogonality.

Grazzi speċjali:

• Il-folks tajba fil U2U u l-għodda query tagħhom.
• Michael Hoffer l-kbir "titgħallem billi tagħmel" blog post, kummenti u r-reazzjonijiet.

</aħħar>

Abbona għall-blog tiegħ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 hawn). 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, Jien għamilt dan li ġej:

• 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" ħsieb.

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

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.

</aħħar>

Abbona għall-blog tiegħi!