I’m using a calendar to track panel discussions on a given day. I have two sessions: morning and afternoon. I want to create a view that shows morning sessions only listed alphabetically via a session ID. This is a little tricky to accomplish (galdu dut zerbait erreala, begi-bistakoa ez bada behintzat).

I can easily create a filtered view showing just that day’s events. The calendar will show all those events and if they all take place on the same hour, it lists them side by side in the hour slot. That’s great. The tricky part is that, lehenetsi, it wants to list them in ID format. Beraz,, if I add "Session 02" and then "Session 01" egutegian, horiek erakusten ditu, ordena horretan (I.E, Session 02 eta, ondoren, Session 01). To list them in Session ID order, Gauza horiek saiatu pentsatu nuen:

1. Configure the view using the web user interface. No luck. There are no options to sort items this way.

   Ez zuen lan noiztik, I am now hoping there’s a CAML query somewhere in there that will allow me to override the sort. CQWP lets me make that kind of change, agian egutegia izango baita?

2. Editatu web zatia, look for an "export" funtzioa eta … BZZZT! I can’t export its XML. There is no export option.

   I’m still holding out hope that I can find and modify some CAML query. Since I can’t export the web part, uzten SharePoint Designer.

3. I add the calendar web part to a sandbox site and open that site using SharePoint Designer. I look at the markup for the web part and I find what I’m looking for. It’s encoded madness, baina ez da: "<ListViewXml …. >kodetuta eromena</ListViewXml>". Zehazki, altxor hau ez da:

<Kontsulta>
<Non>
<DateRangesOverlap>
<FieldRef Name="EventDate"/>
<FieldRef Name="EndDate"/>
<FieldRef Name="RecurrenceID"/>
<Value Type="DateTime">
<Hileko />
</Balio>
</DateRangesOverlap>
</Non>
<OrderBy><FieldRef Name="Session_x0020_ID" /></OrderBy>
</Kontsulta>

(Dekodetu dut &lt;'S eta &GT eta zatitu itzazu hainbat lerro argitasun horrek onerako).

Gehitu <OrderBy> pixka bat, eta, gaur egun, mota Session ID arabera, Ez barneko zerrendako elementu ID.

Erraldoi punta o’ a kapela Becky Isserman bere Isha Sagi-ren blog post iruzkina: http://www.sharepoint-tips.com/2008/07/caml-sorting-by-file-name.html. I wouldn’t have put the <OrderBy> iruzkin gabe bere lekuan.

Hau argiago idazteko pantaila plano batekin, laster espero dut, baina kasu horretan ez dut sekula egin, gutxienez, askoz ere hau egin nuen.

</amaiera>

Gastatzen dugu, kolektiboki pentsatzeko denbora asko SharePoint irtenbide buruzko — Nola hartu, zein tresna erabili, zer gertatzen den zabaldu badute, tenporizadorea lanpostu, esparru, etc. We spend so much time thinking about the up-front bits that it’s easy to forget that we need to retract them as well. Retracting solutions is probably more difficult, diseinu kontzeptuala ikuspegitik, than deploying them. Deployment is basically a cookbook affair. Typically, instalatu ezaugarri bat, Agian Ezaugarri hartzailea kargatu datu batzuk zerrenda batean sartu, that sort of thing. Hala eta guztiz ere, atzera botatzea da potentzialki konplexuagoa.

Eman konponbidea horrelako artifacts sor ditzake:

• Eduki mota
• Zerrenda definizioa
• Gune definizioa
• Zerrenda bat datu
• Nahiz eta hargailuak
• InfoPath inprimakiak

Zerrendan doa.

Da, jakina, garrantzitsua irtenbide bat instantiates artifacts horiek behar bezala diseinatzeko, it’s just as important to consider the update and delete cases. If your solution creates a new list and populates that list with data, zer gertatzen den irtenbidea da atzera? In some cases, the list should be deleted. In other cases, it should be left intact for historical purposes. Your business requirements will guide you to the right decision.

Hau laguntzeko, create a matrix that lists each artifact your solution deploys to SharePoint. List three columns per artifact, bat sortu, eguneratu eta ezabatu. For each case, zehazteko, eragiketa horren emaitza zuzena.

This sort of analysis is obviously best done before the solution is ever deployed to a SharePoint farm. Hala eta guztiz ere, erretzea bezalako, it’s never too late to start doing things correctly. Create that matrix and develop a plan to address the missing update/delete scenarios. It may be a hard problem to solve, baina, gutxienez, jarri beharko duzu kaxa bat arazoaren inguruan.

</amaiera>

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin