Suas chun dáta: An anonymous poster left a great comment about internal names. Be sure to read it.

Nuair a bheidh ag obair le glacadóirí ócáid ​​agus cód eile gur tagairtí míreanna liosta SharePoint tríd an tsamhail réad, Déanaim botúin go minic a ghineann an earráid seo ar runtime:

Earráid Conchango.xyzzyEventReceiver glacadóir luchtú agus a reáchtáil ócáid ​​i xyzzy, Leagan 1.0.0.0 =, Cultúr = neodrach, 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. Mar sin féin, one simple explanation is that I’m referencing a field incorrectly. If the name of the field is "Due Date", Caithfidh mé tagairt dó mar seo i glacadóir ócáid:

properties.ListItem["Due Date"]

Nuair a bheidh mé misspell nó úsáid an cás mícheart nuair tagairt don réimse, SharePoint generates the above mentioned runtime error. Mar shampla, tá sé seo mícheart:

properties.ListItem["due Date"]

</deireadh>

Liostáil le mo bhlag.

D'fhonn a bheith ag obair ar fud an fhadhb PTF Scríobh mé faoi anseo, 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) ní dhéanann na húsáideoirí deiridh a fhios bith níos fearr agus 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, nach bhfuil an deireadh an domhain.

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. Mar thoradh air sin, tá sé ina píosa císte a choinneáil ar an fillteán tuismitheora 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").Fofhillteáin;
  SPFolder fillteán a cuireadh leis = srcFolders.Add(properties.ListItem.ID.ToString());

  SPContentTypeId kpiCT = nua SPContentTypeId("0x0120002A666CAA9176DC4AA8CBAA9DC6B4039F");
  addedFolder.Item["Content Type ID"] = kpiCT;
  addedFolder.Item.Update();

Chun teacht ar an Ábhar Cineál haitheantas iarbhír, Rochtain agam go cineál ábhar trí suímh láithreán agus cóipeáil / a ghreamú sé as an URL mar a thaispeántar:

</deireadh>

Liostáil le mo bhlag!

Is fuath liom a admháil go, 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:

príobháideach neamhní UpdateParentFolder(SPItemEventProperties airíonna)
{

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


} // UpdateParentFolder

Sa chás seo, Tá mé ag obair le leabharlann doiciméad agus na hairíonna atá ag teacht ó ócáid ​​ItemAdded.

Is é an cleas nach féidir leat a fháil ar an SPFolder na míre díreach ó na míre féin (i.e. Is properties.ListItem.Folder null). Ina áit sin, téigh go dtí an mír liosta ar Comhad a bhaineann agus a fháil ar an fillteán Comhad ar.

</deireadh>

Liostáil le mo bhlag!

I’m sure I’m not the first person to come up with this. Mar sin féin, I haven’t noticed anyone publish a trick like this since I started paying close attention to the community last July. Mar sin,, Shíl mé sa phost é seo tip debug tapaidh agus éasca.

Tá mé ag obair ar glacadóir ócáid ​​a thosaigh a ghiniúint an earráid sa 12 hive:

Earráid Conchango.xyzzyEventReceiver glacadóir luchtú agus a reáchtáil ócáid ​​i xyzzy, Leagan 1.0.0.0 =, Cultúr = neodrach, PublicKeyToken = blahbalhbalh. Additional information is below. : Cuspóir tagartha nach leagtar ar shampla de rud.

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.

Rinne mé an réiteach seo a fháil ar mo PDB i ann le súil go SharePoint ar 12 Bheadh ​​hive thaispeáint ar an rian chairn, but no luck. I don’t know if it’s possible and if someone does, cuir in iúl dom 🙂

Tá a fhios agam go bhfuil sé indéanta go do theachtaireachtaí logáil féin a scríobh chuig an 12 hive. Frankly, Theastaigh uaim rud éigin a bhí beagán níos lú scary agus níos tapúla a chur i bhfeidhm.

Rith sé liom go raibh mé in ann ar a laghad, a fháil ar roinnt eolais rian bhunúsach ag breith agus ath-throwing eisceachtaí cineálach mar seo:

  iarracht {
    UpdateEditionDate(airíonna);
  }
  ghabháil (Eisceacht agus)
  {
    caith nua Eisceacht("Dispatcher, UpdateEditionDate(): Eisceacht: [" + e.ToString() + "].");
  }

Léirigh sé seo suas sa 12 hive thusly:

Earráid Conchango.xyzzyEventReceiver glacadóir luchtú agus a reáchtáil ócáid ​​i xyzzy, Leagan 1.0.0.0 =, Cultúr = neodrach, PublicKeyToken = blahblahblah. Additional information is below. : Dispatcher, UpdateEditionDate(): Eisceacht: [System.NullReferenceException: Cuspóir tagartha nach leagtar ar shampla de rud. at Conchango.xyzzyManagementEventReceiver.UpdateEditionDate(Airíonna SPItemEventProperties) at Conchango.xyzzyManagementEventReceiver.Dispatcher(Airíonna SPItemEventProperties, EventDescription Teaghrán)].

Sin a thug dom go léir na sonraí is gá dom a rianú síos ar an bhfadhb ar leith agus tá mé ag súil é a úsáid go leor ag dul ar aghaidh.

</deireadh>

Liostáil le mo bhlag!

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" leis an tréith bhfianaise an cheist.

Mo scéal:

• Ar Dé Luain, Mé a uaslódáil doiciméad agus roinnt sonraí meta sholáthar.
• An tseachtain seo a leanas, 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").
• Cruthaithe againn ar aghaidh seirbhís gréasáin a sholáthraíonn comhéadan BDC-chairdiúil leis an liosta ionas gur féidir le húsáideoirí a aimsiú go héasca an doiciméad Dé Luain trí chuardach teidil.
• A BDC data column provides a friendly user interface. (Tá sé seo mar chuid de mo iarracht ag baint úsáide as BDC ar feadh colún Lookup níos cairdiúla).

Úsáideann an aghaidh a BDC seirbhís deiridh ar cheist mar seo a dhéanamh ar an lookup:

 // Úsáidte uirlis U2U chun cabhrú ghiniúint an cheist CAML.
      oQuery.Query =
        "<I gcás>";

      más rud é (titleFilter.Length > 0)
        oQuery.Query   =
          "  <Agus>";

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

      más rud é (titleFilter.Length > 0)
        oQuery.Query   =
          "    <Tá>" +
          "      <FieldRef Name=\"Title\" />" +
          "      <Value Type=\"Text\">" + titleFilter + "</Luach>" +
          "    </Tá>" +
          "  </Agus>";
      oQuery.Query   =
        "</I gcás>";

Le linn an gcéad chéim na forbartha, this worked great. Mar sin féin, thugamar isteach fillteáin isteach an t-eolaire a réiteach roinnt fadhbanna agus go tobann, 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 chruthú dúinn fillteán atá bunaithe ar an mír liosta ID agus ansin bogadh an comhad ann (Scríobh mé faoi sin anseo; tá muid go raibh torthaí measctha leis an gcur chuige seo, ach ar an iomlán, tá sé ag obair go maith). 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 = nua SPQuery();

Úsáid mé ina ionad sin Cruthaitheoir atá sonraithe d'fhonn:

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

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

Sin réiteach ar an bhfadhb agus thosaigh mé a fháil ar mo torthaí.

I then added the CONTAINS operator into the mix and it broke again. It turns out that the CONTAINS operator, a mhéid is féidir liom a rá, nach bhfuil ag obair leis an dearcadh ar an mbealach céanna leis an a GEQ níos simplí / LEQ operators. I did some searching and learned that the query’s ViewAttributes should be set to "Recursive", mar atá i:

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

That solved the problem for CONTAINS. Go deimhin, seo a réiteach freisin mo fhadhb cuardaigh bunaidh agus dá mbeadh sonraithe mé an tréith recursive an chéad uair, Ní ba mhaith liom a bheith ar siúl ar an cheist arís.

Ar an bhfíric go n-oibríonn SPQuery dearcadh-bhunaithe le haghaidh roinnt oibreoirí (GEQ/LEQ) agus ní daoine eile (BhFUIL), chomh maith leis an bhfíric nach bhfuil KPI cosúil a bheith ag obair ar chor ar bith le leabharlanna doiciméad fillteán iontu mar thoradh ar dom chun a chreidiúint go bhfuil go SPQuery roinnt saincheisteanna orthogonality.

Go raibh maith agat Speisialta:

• Na folks maith ag U2U agus a n-uirlis fhiosraithe.
• Michael Hoffer ar mór "foghlama ag déanamh" blog post, tuairimí agus freagraí.

</deireadh>

Liostáil le mo bhlag!

Suas chun dáta 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. Cur síos mé go bhealach níos mine beag anseo.

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 (ag baint úsáide as teicníc cosúil leis an méid a scríobh mé faoi anseo). 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" ach ina ionad sin a chruthú ar an docs go háitiúil agus ansin iad a uaslódáil).

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

Tá sé seo de ghnáth simplí a dhéanamh agus mé cur síos ar rud éigin go mór mar seo ag an Beagle SharePoint le go leor de shots scáileán má tá suim agat.

In a nutshell, Rinne mé an méid seo a leanas:

• Create a view on the doc library called "Pending".
• Cumraigh an dearcadh neamhaird a struchtúr fillteán.
• Cruthaigh Liosta PTF.
• Create an indicator in the list that points to the doc lib and that "Pending" féachaint ar.

This simply does not work. The KPI shows my target (e.g. Cúig cinn de dhoiciméid práinneach) 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.

</deireadh>

Liostáil le mo bhlag!

I was working on a feature last week that would add some event receivers to a specific list instance. (Blogged mé beagán faoi go glacadóir liosta anseo).

Ag baint úsáide as an líne ordaithe, Raibh mé in ann a shuiteáil an gné gan aon earráid (ach féach thíos le haghaidh an earráid i bhfolach). When I tried to deploy the feature on the site, MOSS complained of a "FileNotFoundException" earráid. This blog entry describes how I solved it.

This is the error that MOSS showed me in the web browser:

Feature ‘b2cb42e3-4f0a-4380-aaba-1ef9cd526f20’ could not be installed because the loading of event receiver assembly "xyzzyFeatureReceiver_0" failed: System.IO.FileNotFoundException: Could not load file or assembly ‘xyzzyFeatureReceiver_0’ nó ceann dá spleáchais. The system cannot find the file specified. File name: ‘xyzzyFeatureReceiver_0’ at System.Reflection.Assembly.nLoad(AssemblyName ainm comhaid, Codebase Teaghrán, AssemblySecurity Fianaise, Tionól locationHint, StackCrawlMark& ithir Stack, Boole throwOnFileNotFound, ForIntrospection Boole) at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, AssemblySecurity Fianaise, StackCrawlMark& ithir Stack, ForIntrospection Boole) at System.Reflection.Assembly.InternalLoad(String assemblyString, AssemblySecurity Fianaise, StackCrawlMark& ithir Stack, ForIntrospection Boole) 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) go 1. Tabhair faoi deara: 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. Ach, 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. Mar sin féin, 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.

Ar Aghaidh, I went to the trouble of enabling the "assembly bind failure log" (following the helpful and accurate instructions provided) 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. Ach … it won’t search for it in the 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" for feature b2cb42e3-4f0a-4380-aaba-1ef9cd526f20: System.ArgumentNullException: Ní féidir luach a bheith ar neamhní. Ainm Paraiméadar: cineál at System.Activator.CreateInstance(Type type, Boolean nonPublic) at System.Activator.CreateInstance(Type type) at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject() Troubleshoot issues with Windows SharePoint Services.

Time for one last trip to the Internets!

This time I find out, predictably enough, that MOSS issues this error because the assembly is not in GAC.

Ba mhaith liom a fháil ar rud éigin as dhearfach seo agus iarracht a bhraitheann ar beag bródúil go chruthaigh mé an Teifeacha de tionóil MSIL, but it’s not working. I’m just plain annoyed. I find myself muttering "chicken or the egg" faoi ​​mo anáil.

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" ach ní féidir teacht ar aon).

Shuiteáil mé an gné agus a ghníomhachtú é agus … oibríonn sé! Mar sin,, tar éis an tsaoil go, I had to basically ‘reboot’ my project. This is another reason why I hate computers.

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. Ar chúis éigin, I did not use the -force option when I installed the new project. An uair seo, Rinne mé i ndáiríre, truly forget to copy this new project’s assembly into the GAC. Mar thoradh air sin, I received that "FielNotFoundException" earráid. An uair seo, Fuair ​​mé é ó stsadm, not when I tried to activate the feature via the web browser. Mar sin,, -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.

</deireadh>

Suas chun dáta: This works but there are significant limitations which are described in the comments. This may still be useful in some cirumstances.

Suas chun dáta 2: I mo tionscadal reatha, users always upload documents. Mar thoradh air sin, 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() Breathnaíonn an glacadóir le haghaidh luach bailí ann roimh iarbhír ag comhlíonadh a athainmniú agus ó shin, 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()" modh. Ina áit sin, úsáidimid "MoveTo(…)". Here is a minimal bit of code to accomplish this:

 poiblí shárú neamhní ItemAdded(SPItemEventProperties airíonna)
        {
            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.

Is é seo an leagan níos úsáidí a dhéanann an rud céanna, but assigns the name of the file to "Title":

 poiblí shárú neamhní ItemAdded(SPItemEventProperties airíonna)
        {
            DisableEventFiring();

            // An teideal na míre seo a shannadh do ainm an chomhaid féin.
 // NÓTA: Ní mór an tasc a chur i bhfeidhm roimh linn a mhodhnú an comhad féin.
 // Ag glaoch ar thabhairt cothrom le dáta() ar an SPFile is cosúil a dhéanamh neamhbhailí na maoine i
 // ciall éigin.  Updates to "Title" Theip ar go dtí an t-athrú (agus nuashonrú() glaoch)
 // Bhí ar athraíodh a ionad i os comhair an t-athrú ar ainm an chomhaid.
            properties.ListItem["Title"] = Properties.ListItem.File.Name;

            properties.ListItem.Update();

            SPFile f = properties.ListItem.File;

            // Faigh an síneadh ar an gcomhad.  Ní mór dúinn go déanaí.
 teaghrán spfileExt = nua Eolas Comhad(f.Name).Síneadh;

            // Athainmnigh an comhad leis an mír den liosta ID agus úsáid a bhaint as an síneadh comhad a choinneáil
 // an chuid sin de sé slán.
            f.MoveTo(properties.ListItem.ParentList.RootFolder.Url +
                "/" + properties.ListItem["ID"] + spfileExt);

            // Tiomantas an t-aistriú.
            f.Update();

            EnableEventFiring();
        }

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

That column is of type "lookup".

Tá mé modhnaithe <CommonViewFields> agus ItemStyle.xsl a thaispeáint ar an gcolún.

A simplí <XSL:luach-ar roghnú =…> tuairisceáin ar ais luach inmheánach go n-áirítear sonraí seasamh ordinal, mar shampla:

1;#Miami

Chun a fháil ar an luach daonna-chairdiúil, úsáid a bhaint as XSL bhfotheaghrán-tar éis, mar a thaispeántar:

<XSL:value-of select="substring-after(@ Real_x005F_x0020_Estate_x005F_x0020_Location,'#')"></XSL:luach-ar>

Bain úsáid as an teicníc aon uair a bhfuil tú ag obair le luachanna lookup i transforms XSL agus is gá a fháil ar an luach daonna-chairdiúil.

<deireadh />

Suas chun dáta: Jeremy Thake Tá blogged faoi seo agus chur ar bun roinnt cód le haghaidh iarratas consól go léiríonn ainmneacha inmheánacha.

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", Ghlac mé go raibh an t-ainm colún a úsáid i <CommonViewFields> is "Due_x0020_Date".

Mícheart!

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

Conas a raibh a aimsiú liom é? I re-read Heather Iontráil bhlag Sholamón ar mhodhnú CQWP to show additional columns of data. She describes this process at step #13. Trust it. It’s correct. Ar a laghad, 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" ainm, Theastaigh uaim a réimse eile a chur le <CommonViewFields>. Using the Solomon technique, I was getting a column name like "XYZ_x0020_Project_x0020_Due_x00".

Shíl mé go féin, 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.

Bónas tip: Nuair a bhí mé ag obair leis an CQWP, má chuir mé ainm inmheánach dona <CommonViewFields>, the CQWP would tell me that the query had returned no results. Ach, má chuir mé cineál sonraí chuig an t-ainm réimse, 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, ach nuair a rinne mé a chur ar taispeáint a luach, I would always get a blank.

Ní raibh an masc an earráid:

<CommonViewFields>Due_x0020_Date;</CommonViewfields>

Seo raibh masc an earráid:

<CommonViewFields>Due_x0020_Date,Datetime;</CommonViewfields>

</deireadh>