АБНАЎЛЕННЕ: An anonymous poster left a great comment about internal names. Be sure to read it.

Пры працы з падзеяй прымачоў і іншы код, які спасылаецца SharePoint элементы спісу праз аб'ектную мадэль, Я часта робяць памылкі, якія генеруюць гэтую памылку падчас выканання:

Памылка загрузкі і запуску Conchango.xyzzyEventReceiver прымача падзей у XYZZY, Version = 1.0.0.0, Культура = нейтральнай, 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. Аднак, one simple explanation is that I’m referencing a field incorrectly. If the name of the field is "Due Date", Я павінна звяртацца да яе, як гэта ў прыёмніку падзей:

properties.ListItem["Due Date"]

Калі я арфаграфічнымі памылкамі або выкарыстоўваць няправільныя выпадку пры звароце да поля, SharePoint generates the above mentioned runtime error. Напрыклад, гэта няправільна:

properties.ListItem["due Date"]

</канец>

Падпісацца на мой блог.

Для таго, каб абыйсці праблемы 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, якi не з'яўляецца канцом святла.

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. У выніку, гэта кавалак пірага, каб захаваць бацькоўскай тэчкі 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("Дакументы").SubFolders;
  SPFolder дабаўленая папка = srcFolders.Add(properties.ListItem.ID.ToString());

  SPContentTypeId kpiCT = новы SPContentTypeId("0x0120002A666CAA9176DC4AA8CBAA9DC6B4039F");
  addedFolder.Item["Content Type ID"] = kpiCT;
  addedFolder.Item.Update();

Каб знайсці фактычнага ідэнтыфікатара тыпу кантэнту, Я атрымаў доступ, што тып кантэнту праз сайт налады і капіяваць / ўставіць яго з URL, як паказана:

</канец>

Падпісацца на мой блог!

Я ненавіджу прызнавацца ў гэтым, 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, Version = 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 туды з надзеяй, што ў SharePoint 12 вулей пакажа трасіроўку стэка, but no luck. I don’t know if it’s possible and if someone does, калі ласка, дайце мне ведаць, 🙂

Я ведаю, што гэта магчыма напісаць свой уласны часопіс паведамленняў 12 вулей. Frankly, Я хацеў нешта крыху менш страшным і хутчэй рэалізаваць.

Мне прыйшло ў галаву, што я магу па крайняй меры атрымаць некаторую базавую інфармацыю следу, ловячы і зноў кідалі агульных выключэнняў, як гэта:

  старацца {
    UpdateEditionDate(ўласцівасці);
  }
  злавіць (Выключэнне і)
  {
    кідаць новы Выключэнне("Dispatcher, UpdateEditionDate(): Выключэнне: [" + e.ToString() + "].");
  }

Гэта выявілася ў 12 вулей канстанты выглядае так:

Памылка загрузкі і запуску Conchango.xyzzyEventReceiver прымача падзей у XYZZY, Version = 1.0.0.0, Культура = нейтральнай, PublicKeyToken = blahblahblah. Additional information is below. : Дыспетчар, UpdateEditionDate(): Выключэнне: [System.NullReferenceException: Спасылка на аб'ект не паказвае на асобнік аб'екта. at Conchango.xyzzyManagementEventReceiver.UpdateEditionDate(SPItemEventProperties ўласцівасці) at Conchango.xyzzyManagementEventReceiver.Dispatcher(SPItemEventProperties ўласцівасці, Струнны EventDescription)].

Гэта дало мне ўсё падрабязна мне трэба было адшукаць гэтай канкрэтнай праблемы, і я чакаю, каб выкарыстоўваць яго шмат у будучыні.

</канец>

Падпісацца на мой блог!

На мінулым тыдні я быў рэалізацыі "развіваецца" solution for a client that uses BDC and SPQuery and ran into some difficulty using SPQuery against a document library containing folders. Вынік: прызначыць "рэкурсіўны" да меркавання атрыбут запыту.

Мой сцэнар:

• У панядзелак, Я загрузіць дакумент і паставіць некаторыя мета-дадзеных.
• 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["Дакументы"];

SPQuery oQuery = новы SPQuery();

I instead used a constructor that specified a view:

SPList oList = web.Lists["Дакументы"];

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

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, Я зрабіў наступнае:

• 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" глядзець.

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

Мне здаецца, што нават калі вы паказаць выгляд, the KPI doesn’t honor the "show all items without folders" ўстаноўка і замест, абмяжоўваецца ў каранёвую тэчку.

Калі я не мае рацыю, калі ласка, напішыце мне або пакінуць каментар.

</канец>

Падпісацца на мой блог!

I was working on a feature last week that would add some event receivers to a specific list instance. (Я пісаў трохі аб гэтым спісе прымачом тут).

Выкарыстанне каманднага радка, Я магу ўсталяваць кампанент без памылкі (але гл ніжэй для схаванай памылцы). When I tried to deploy the feature on the site, MOSS complained of a "FileNotFoundException" памылка. This blog entry describes how I solved it.

Гэта памылка, якая паказала мне MOSS ў вэб-браўзэры:

Feature ‘b2cb42e3-4f0a-4380-aaba-1ef9cd526f20’ could not be installed because the loading of event receiver assembly "xyzzyFeatureReceiver_0" не ўдалося: System.IO.FileNotFoundException: Could not load file or assembly ‘xyzzyFeatureReceiver_0’ або адзін з залежных ад. The system cannot find the file specified. File name: ‘xyzzyFeatureReceiver_0’ at System.Reflection.Assembly.nLoad(AssemblyName імя_файла, Струнны CODEBASE, Доказы assemblySecurity, Асамблея locationHint, StackCrawlMark& стэк глебы, Булевы throwOnFileNotFound, Булевы forIntrospection) at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Доказы assemblySecurity, StackCrawlMark& стэк глебы, Булевы forIntrospection) at System.Reflection.Assembly.InternalLoad(String assemblyString, Доказы assemblySecurity, StackCrawlMark& стэк глебы, Булевы forIntrospection) at System.Reflection.Assembly.Load(String assemblyString) at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject() WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) да 1. Увага: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. Troubleshoot issues with Windows SharePoint Services.

I know how to deliberately cause that error: don’t install the assembly in the GAC. Але, it was in the GAC. I normally install assemblies into the GAC by dragging them into the c:\windows\assembly folder using windows explorer. I’ve never felt 100% comfortable doing that because I always thought that gacutil existed for a reason … so I tried that. It made no difference.

I searched the Internets and found this post: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2243677&SiteID=1

The poster happened to be using the same root bit of code (from the Inside WSS book from this list) so that was a hopeful sign. Аднак, the suggestion of decorating the assembly with an [assembly: ] directive didn’t make sense to me. I tried it anyway and I was right. It made no difference.

Then I noticed that my class definition was not public. I made it public and that made no difference.

Наступны, I went to the trouble of enabling the "assembly bind failure log" (пасля карыснымі і дакладнымі інструкцыямі) and this is where things started to get interesting. That log shows me that the runtime is searching everywhere on that server for my assembly. It even appears to be searching for it in my medicine cabinet. Але … ён не будзе шукаць яго ў GAC.

I put on my winter jacket and go searching the Internets again and find that someone has had this problem too. The lengthy discussion in that posting peters off into nothing and I can’t find a solution.

I move my assembly into one of the places the log claims it’s searching and I make a little more progress. I’m rewarded with a new error in the browser when I try to activate the feature:

Failed to create feature receiver object from assembly "xyzzyFeatureReceiver_0", type "Conchango.xyzzyFeatureReceiver" для мастацкіх b2cb42e3-4f0a-4380-ааба-1ef9cd526f20: System.ArgumentNullException: Значэнне не можа быць пустым. Найменне параметра: тып at System.Activator.CreateInstance(Тып Тып, Булевы непублічнай) at System.Activator.CreateInstance(Тып Тып) at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject() Troubleshoot issues with Windows SharePoint Services.

Час для адной апошняй паездкі ў інтэрнэце!

На гэты раз я даведаюся,, дастаткова прадказальна, that MOSS issues this error because the assembly is not in GAC.

Я хачу атрымаць нешта станоўчае з гэтага і спрабуюць адчуваць сябе крыху ганаруся тым, што я стварыў Уцякач з MSIL зборкі, but it’s not working. I’m just plain annoyed. I find myself muttering "chicken or the egg" пад нос.

I finally decide to punt. I create an entirely new project and copy/paste the code from the incredible-cloaked-from-the-GAC-assembly non-working project over to this new project. (I look for a build flag called something like "hide from assembly binding if installed in the GAC" але не магу знайсці адну).

Я ўсталяваць функцыю і актываваць яго і … гэта працуе! Так, пасля ўсяго, што, I had to basically ‘reboot’ my project. Гэта яшчэ адна прычына, чаму я ненавіджу кампутары.

I did learn something useful from this. I had been installing features using the stsadm command line all day long and been using the "-force" option out of habit. Па некаторых прычынах, I did not use the -force option when I installed the new project. На гэты раз, Я зрабіў на самай справе, truly forget to copy this new project’s assembly into the GAC. У выніку, I received that "FielNotFoundException" памылка. На гэты раз, Я атрымаў яго ад Stsadm, not when I tried to activate the feature via the web browser. Так, -force actually plays two roles. It allows you to re-install an existing feature. It also allows you to install a buggy feature that cannot work at runtime by suppressing the error. It probably says as much in the help somewhere but I never noticed it.

</канец>

АБНАЎЛЕННЕ: This works but there are significant limitations which are described in the comments. This may still be useful in some cirumstances.

АБНАЎЛЕННЕ 2: У маім бягучым праекце, users always upload documents. У выніку, I don’t run into a problem where MS Word is running and thinks that the file was renamed on it. I did run into a problem, "the file was modified by someone else" and solved this via a simple semaphore type flag. Users need to change a meta data field from its default value to something else. The itemupdated() Прыёмнік шукае сапраўднае значэнне там да фактычнага выканання перайменавання і з тых часоў, I have not had any problems. Your mileage may vary.

I have a client requirement to change the name of files uploaded to a specific document library to conform with a particular naming convention. The API does not provide a "rename()" метад. Замест, мы выкарыстоўваем "MoveTo(…)". Here is a minimal bit of code to accomplish this:

 грамадскасць адмяняць ануляваць ItemAdded(SPItemEventProperties ўласцівасці)
        {
            SPFile F = properties.ListItem.File;

            f.MoveTo(properties.ListItem.ParentList.RootFolder.Url + "/xyzzy.doc");
            f.Update();

        }

The only tricky bit is the "properties.ListItem.ParentList.RootFolder.Url". The MoveTo() method requires a URL. That mashed up string points me to the root folder of my current document library. This allows me to avoid any hard coding in my event receiver.

Гэта больш карысна версія, якая робіць тое ж самае, but assigns the name of the file to "Title":

 грамадскасць адмяняць ануляваць ItemAdded(SPItemEventProperties ўласцівасці)
        {
            DisableEventFiring();

            // Назначце назва гэтага пункта на імя самога файла.
 // УВАГА: Гэта прызначэнне павінна адбыцца, перш чым змяніць сам файл.
 // Выклік абнаўлення() на SPFile здаецца несапраўдным ўласцівасці ў
 // пэўным сэнсе.  Updates to "Title" не ўдалося пакуль што змены (і абнаўлення() называць)
 // былі перамешчаныя перад змяненнем імя файла.
            properties.ListItem["Title"] = Properties.ListItem.File.Name;

            properties.ListItem.Update();

            SPFile F = properties.ListItem.File;

            // Атрымаць пашырэння файла.  Нам трэба, каб пазней.
 радок spfileExt = новы Інфармацыя аб файле(f.Name).Пашырэнне;

            // Пераназавіце файл у ID элемента спісу і выкарыстоўваць пашырэнне файла, каб захаваць
 // што частка яго ў такім выглядзе.
            f.MoveTo(properties.ListItem.ParentList.RootFolder.Url +
                "/" + properties.ListItem["ID"] + spfileExt);

            // Фіксацыя ходу.
            f.Update();

            EnableEventFiring();
        }

I have a column name in a content type named "Real Estate Location".

That column is of type "lookup".

Я змяніў <CommonViewFields> і ItemStyle.xsl паказаць калонкі.

Просты <XSL:кошт з абярыце =…> вяртаецца ўнутранае значэнне, якое ўключае парадкавых дадзеных пазіцыі, такі як:

1;#Маямі

Каб атрымаць зразумелыя чалавеку значэнні, выкарыстоўваць XSL-падрадкоў пасля, як паказана на малюнку:

<XSL:value-of select="substring-after(@ Real_x005F_x0020_Estate_x005F_x0020_Location,'#')"></XSL:коштам ад>

Выкарыстоўвайце гэты метад, калі вы працуеце з пошуку значэнняў у пераўтварэнні XSL і трэба, каб зразумелыя чалавеку значэнні.

<канец />

АБНАЎЛЕННЕ: Джэрэмі Thake была блогу пра гэта і мірыцца некаторыя код для кансольнага прыкладання які паказвае ўнутраныя імёны.

I was trying to get a content query web part to display a due date from a task and because the screen label is "Due Date", Я выказаў меркаванне, што імя слупка для выкарыстання ў <CommonViewFields> is "Due_x0020_Date".

Няправільны!

The real column name in this case was "DueDate".

Як я лічу, гэта? I re-read Heather Блог Саламона ўваход на змены CQWP to show additional columns of data. She describes this process at step #13. Trust it. It’s correct. Па крайняй меры, it was correct for me. I did not trust it at first for another column with a much longer name.

I say "Trust it" because I did not trust it and probably wasted near two hours butting my head up against a wall. After I resolved the "DueDate" імя, Я хацеў дадаць яшчэ адно поле <CommonViewFields>. Using the Solomon technique, I was getting a column name like "XYZ_x0020_Project_x0020_Due_x00".

Я падумаў пра сябе, that’s clearly a truncated name. I went ahead and un-truncated it with no success. I finally used the seemingly truncated name and it worked.

Бясплатны савет: Калі я працаваў з CQWP, Калі я дадала дрэнная ўнутраная імя <CommonViewFields>, the CQWP would tell me that the query had returned no results. Але, Калі я дадаў тыпу дадзеных да імя поля, it would return a result. Adding the data type actually masked a problem since I was referencing a non-existent field. I could add it, але калі я паспрабаваў адлюстраваць яго значэнне, I would always get a blank.

Гэта не маскіраваць памылку:

<CommonViewFields>Due_x0020_Date;</CommonViewFields>

Гэтага маскіраваць памылкі:

<CommonViewFields>Due_x0020_Date,DateTime;</CommonViewFields>

</канец>