UPDATE: An anonymous poster left a great comment about internal names. Be sure to read it.

Kur punon me marrës ngjarje dhe kodin tjetër që referencat artikuj listë SharePoint nëpërmjet modelit objekt, Unë shpesh bëjnë gabime që gjenerojnë këtë gabim në runtime:

Ngarkimin dhe drejtimin Error ngjarje marrës Conchango.xyzzyEventReceiver në xyzzy, Version = 1.0.0.0, Culture = neutral, PublicKeyToken = 0dc50a750396c3ac. Additional information is below. : Value does not fall within the expected range.

I think this is a fairly generic error that is potentially caused many different ways. Megjithatë, one simple explanation is that I’m referencing a field incorrectly. If the name of the field is "Due Date", I must reference it like this in an event receiver:

properties.ListItem["Due Date"]

When I misspell or use the wrong case when referencing the field, SharePoint generates the above mentioned runtime error. Për shembull, this is wrong:

properties.ListItem["due Date"]

</fund>

Abonohen në blogun tim.

Në mënyrë për të punuar rreth një problem KPI Kam shkruar në lidhje me këtu, 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) përdoruesit përfundimtarë nuk e di ndonjë më të mirë dhe 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, cila nuk eshte fundi i botës.

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. Si rezultat, kjo është një copë tortë për të mbajtur dosje prindi 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 = i ri SPContentTypeId("0x0120002A666CAA9176DC4AA8CBAA9DC6B4039F");
  addedFolder.Item["Content Type ID"] = KpiCT;
  addedFolder.Item.Update();

Për të gjetur aktuale Lloji ID Content, Unë disponim se tipi i përmbajtjes nëpërmjet settings vend dhe kopje / ngjit atë nga URL, siç tregohet:

</fund>

Abonohen në blogun tim!

Unë e urrej të pranoj atë, 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 pavlefshme UpdateParentFolder(SPItemEventProperties Prona të paluajtshme)
{

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


} // UpdateParentFolder

Në këtë rast, 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). Në vend të kësaj, go to the list item’s associated File and get the File’s folder.

</fund>

Abonohen në blogun tim!

I’m sure I’m not the first person to come up with this. Megjithatë, I haven’t noticed anyone publish a trick like this since I started paying close attention to the community last July. Kështu, Unë mendova se do të postoj atë këtë tip të shpejtë dhe të lehtë debug.

I’m working on an event receiver that started to generate this error in the 12 zgjua:

Ngarkimin dhe drejtimin Error ngjarje marrës Conchango.xyzzyEventReceiver në xyzzy, Version = 1.0.0.0, Culture = neutral, PublicKeyToken=blahbalhbalh. Additional information is below. : Object reference nuk është caktuar për një shembull të një objekti.

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 tried this solution to get my pdb in there with hopes that SharePoint’s 12 hive would show the stack trace, but no luck. I don’t know if it’s possible and if someone does, please let me know 🙂

I know it’s possible to write your own log messages to the 12 zgjua. Frankly, I wanted something a little less scary and quicker to implement.

It occurred to me that I could at least get some basic trace information by catching and re-throwing generic exceptions like this:

  mundohem {
    UpdateEditionDate(Prona të paluajtshme);
  }
  kap (Exception e)
  {
    hedh i ri Exception("Dispatcher, UpdateEditionDate(): Exception: [" + e.ToString() + "].");
  }

This showed up in the 12 hive thusly:

Ngarkimin dhe drejtimin Error ngjarje marrës Conchango.xyzzyEventReceiver në xyzzy, Version = 1.0.0.0, Culture = neutral, PublicKeyToken=blahblahblah. Additional information is below. : Dispatcher, UpdateEditionDate(): Exception: [System.NullReferenceException: Object reference nuk është caktuar për një shembull të një objekti. at Conchango.xyzzyManagementEventReceiver.UpdateEditionDate(Pronat SPItemEventProperties) at Conchango.xyzzyManagementEventReceiver.Dispatcher(Pronat SPItemEventProperties, String eventDescription)].

That gave me all the detail I needed to track down that particular problem and I expect to use it a lot going forward.

</fund>

Abonohen në blogun tim!