به منظور کار در اطراف یک مشکل KPI من در مورد اینجا نوشت, 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. 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 = جدید 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:

خصوصی از درجه اعتبار ساقط UpdateParentFolder(SPItemEventProperties خواص)
{

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


} // UpdateParentFolder

در این مورد, 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 (i.e. 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. پس, من فکر کردم من می خواهم آن را آسان و سریع اشکال زدایی نوک ارسال.

من کار بر روی یک گیرنده رویداد آغاز شده است که برای تولید این خطا در 12 کندو:

خطا در بارگذاری و در حال اجرا رویداد Conchango.xyzzyEventReceiver گیرنده در xyzzy, نسخه = 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.

من سعی کردم این راه حل به PDB من در آن وجود دارد با این امید که شیرپوینت 12 کندو ردیابی پشته را نشان می دهد, اما هیچ شانس. I don’t know if it’s possible and if someone does, لطفا اجازه دهید من می دانم 🙂

من می دانم که این امکان وجود دارد نوشتن پیام های ورود به سیستم خود را به 12 کندو. Frankly, من می خواستم چیزی کمی کمتر ترسناک و سریعتر برای پیاده سازی.

آن را به من رخ داده است که من می توانم حداقل برخی از اطلاعات اولیه اثری با فیلم برداری و دوباره پرتاب استثنا کلی مثل این:

  امتحان {
    UpdateEditionDate(خواص);
  }
  گرفتن (استثنا الکترونیکی)
  {
    پرتاب جدید استثنا("Dispatcher, UpdateEditionDate(): استثنا: [" + e.ToString() + "].");
  }

این نشان داد در 12 کندو thusly:

خطا در بارگذاری و در حال اجرا رویداد Conchango.xyzzyEventReceiver گیرنده در xyzzy, نسخه = 1.0.0.0, فرهنگ = بی طرف, PublicKeyToken = blahblahblah. Additional information is below. : اعزام کننده, UpdateEditionDate(): استثنا: [System.NullReferenceException: مرجع شی به یک نمونه از یک شی تنظیم نشده. at Conchango.xyzzyManagementEventReceiver.UpdateEditionDate(خواص SPItemEventProperties) at Conchango.xyzzyManagementEventReceiver.Dispatcher(خواص SPItemEventProperties, eventDescription رشته)].

که به من تمام جزئیات مورد نیاز برای پیگیری کردن آن مشکل خاص و من انتظار دارم به استفاده از آن را بسیار رفتن به جلو.

</پایان>

مشترک شدن در وبلاگ من!

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:

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

SPQuery oQuery = جدید SPQuery();

I instead used a constructor that specified a view:

SPList 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. 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 اینجا). 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".

انجام این کار معمولاً ساده است و من چیزی شبیه به این را در شیرپوینت بیگل توصیف کردم با تعداد زیادی عکس از صفحه نمایش اگر علاقه دارید.

به طور خلاصه, من زیر:

• Create a view on the doc library called "Pending".
• نمای را طوری پیکربندی کنید که ساختار پوشه را نادیده بگیرد.
• یک لیست KPI ایجاد کنید.
• Create an indicator in the list that points to the doc lib and that "Pending" دیدن.

این به سادگی کار نمی کند. KPI هدف من را نشان می دهد (e.g. پنج سند فوری) اما همیشه تعداد واقعی اسناد فوری را صفر نشان می دهد. به طور متناقض, اگر به جزئیات بپردازید, این پنج سند فوری را در لیست نشان می دهد. 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.

</پایان>

مشترک شدن در وبلاگ من!