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 (sakemm I qbiżt xi ħaġa reali ovvju).

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, b'mankanza, it wants to list them in ID format. Allura, if I add "Session 02" and then "Session 01" il-kalendarju, jurihom f'dik l-ordni (I.E, Sessjoni 02 u mbagħad Sessjoni 01). To list them in Session ID order, Ħsibt li jippruvaw dawn l-affarijiet:

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

   Peress li ma ħadmux, 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, maybe calendar will as well?

2. Edit the web part, look for an "export" function and … 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, that leaves 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, but it’s there: "<ListViewXml …. >encoded madness</ListViewXml>". Speċifikament, hemm dan gem:

<Mistoqsija>
<Fejn>
<DateRangesOverlap>
<FieldRef Name="EventDate"/>
<FieldRef Name="EndDate"/>
<FieldRef Name="RecurrenceID"/>
<Value Type="DateTime">
<Xahar />
</Valur>
</DateRangesOverlap>
</Fejn>
<OrderBy><FieldRef Name="Session_x0020_ID" /></OrderBy>
</Mistoqsija>

(Stajt decoded l- &lt;"Iu &tal gt u maqsuma minnhom għal-linji multipli f'ġieħ iċ-ċarezza).

Żid il- <OrderBy> bit u issa xorta mill Sessjoni ID, mhux l-lista ta 'loġġetti ID intern.

Ġiganteski ponta o’ il-hat biex Becky Isserman għall-kummenti tagħha biex blog post Isha Sagi tal: http://www.sharepoint-tips.com/2008/07/caml-sorting-by-file-name.html. I wouldn’t have put the <OrderBy> fil-post dritt mingħajr kumment tagħha.

Nispera li tikteb dan up aktar ċar fir screen shots malajr, iżda fil-każ I qatt ma, inqas Jien għamilt dan ħafna.

</aħħar>

Aħna flimkien jonfqu ammont kbir ta 'ħin jaħsbu dwar soluzzjonijiet SharePoint — kif toħloq lilhom, li għodda għall-użu, x'jiġri meta dawn jonqsu li tuża, impjiegi timer, ambiti, eċċ. 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, minn perspettiva disinn kunċettwali, than deploying them. Deployment is basically a cookbook affair. Typically, jinstallaw karatteristika, forsi jkunu riċevitur karatteristika tagħbija xi data ġo lista, that sort of thing. Madankollu, retracting huwa potenzjalment aktar kumplessa.

Soluzzjoni mogħti jista 'joħloq artifacts bħal dawn:

• Kontenut Tip
• Lista Definizzjoni
• Site Definizzjoni
• Data fil-lista
• Anke riċevituri
• Forom InfoPath

Il-lista tkompli.

Filwaqt li huwa ovvjament importanti li disinn soluzzjoni li instantiates dawk artifacts korrett, 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, x'jiġri meta s-soluzzjoni tiġi miġbuda lura? 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.

Biex tgħin ma 'dan, create a matrix that lists each artifact your solution deploys to SharePoint. List three columns per artifact, waħda għall joħolqu, update and delete. For each case, jiddeterminaw ir-riżultat korrett għal dik l-operazzjoni.

This sort of analysis is obviously best done before the solution is ever deployed to a SharePoint farm. Madankollu, bħat-tipjip, 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, iżda mill-inqas inti ser ikollok tpoġġi kaxxa madwar il-problema.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin