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. Као резултат тога, 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;
  СПФолдер 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.Item["ZZ Approval Status"] = "Good news, свако!";
thisItemFolder.Item.Update();


} // УпдатеПарентФолдер

У овом случају, Радим у библиотеци докумената и својства долазе из ИтемАддед догађаја.

Трик је у томе да не можете добити СПФолдер на ставке директно из саме ставке (и.е. пропертиес.ЛистИтем.Фолдер је нулл). Уместо тога, идите на вези Филе ставке листе и добити именик фајла.

</крај>

Претплатите се на мој блог!

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. Тако, Мислио сам да је објавите ово брзо и једноставно дојаве дебуг.

Радим на састанак пријемнику који су почели да стварају ову грешку у 12 кошница:

Грешка при учитавању и трчање догађај пријемник Цонцханго.киззиЕвентРецеивер у киззи, Версион = 1.0.0.0, Култура = неутрална, ПублицКеиТокен = блахбалхбалх. 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.

Покушао сам Ово решење да би мој ПДБ тамо са надом да је СхареПоинт 12 кошница ће показати траг стека, but no luck. I don’t know if it’s possible and if someone does, молим вас јавите ми 🙂

Знам да је могуће да се напишете своје поруке да 12 кошница. Frankly, Хтео сам нешто мало мање страшно и брже да спроводи.

Помислила сам да сам барем добити неке основне информације трага за хватање и поново бацају опште изузетке као што је овај:

  покушати {
    УпдатеЕдитионДате(Некретнине);
  }
  улов (Изузетак Е)
  {
    бацити нови Изузетак("Dispatcher, УпдатеЕдитионДате(): Изузетак: [" + е.ТоСтринг() + "].");
  }

Овај се појавио у 12 кошница тхусли:

Грешка при учитавању и трчање догађај пријемник Цонцханго.киззиЕвентРецеивер у киззи, Версион = 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" на вид атрибутом упита.

Мој сценарио:

• У понедељак, Ја отпремите документ и понуде неке мета податке.
• 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" подешавање и уместо тога, стога, само у основну фасциклу.

Ако сам у праву, молим вас пустите ми линију, или оставите коментар.

</крај>

Претплатите се на мој блог!