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 (a non ser que eu perda algo de verdade obvia).

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, por defecto, it wants to list them in ID format. Así, se eu engadir "Sesión 02" e despois da sesión "01" para o calendario, mostra-las nesta orde (i.e, Sesión 02 e, a continuación Sesión 01). To list them in Session ID order, Eu penso que tratar isto:

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

   Sempre que non funcionou, 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, quizais calendario vai ben?

2. Editar a parte web, look for an "export" función e … 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, que deixa SharePoint Design.

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, pero está aí: "<ListViewXml …. >loucura codificada</ListViewXml>". Especificamente, hai esta xoia:

<Pregunta>
<Onde>
<DateRangesOverlap>
<FieldRef Name = "EVENTDATE" />
<FieldRef Name = "EndDate" />
<FieldRef Name = "RecurrenceID" />
<Tipo value = "datetime">
<Mes />
</Valor>
</DateRangesOverlap>
</Onde>
<OrderBy><FieldRef Name = "Session_x0020_ID" /></OrderBy>
</Pregunta>

(Eu teño decodificado o &lt;'S e &gt e división los para fóra varias liñas para unha cuestión de claridade).

Engadir o <OrderBy> pouco e agora clasifica por ID de sesión, non o ID do elemento interna lista.

Xigantesca punta o’ o sombreiro para Becky Isserman polo seu comentario ao post do blog Isha Sagi: http://www.sharepoint-tips.com/2008/07/caml-sorting-by-file-name.html. I wouldn’t have put the <OrderBy> no lugar seguro sen o teu comentario.

Espero escribir isto máis claramente con pantallas en breve, pero no caso eu non fago, polo menos eu fixen iso moi.

</final>

Nós colectivamente gastar moito tempo a pensar sobre o SharePoint solucións — como crealos, cal ferramenta utilizar, o que ocorre cando non poden implantar, traballos de timer, alcance, 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, desde unha perspectiva de deseño conceptual, than deploying them. Deployment is basically a cookbook affair. Typically, instalar un recurso, quizais un receptor de recurso cargar algúns datos nunha lista, that sort of thing. Con todo, retracción é potencialmente máis complexo.

A solución dada pode crear artefactos como estes:

• Tipo de contido
• Definición de lista
• Definición da web
• Datos nunha lista
• Mesmo receptores
• Os formularios de InfoPath

A lista segue.

Aínda que sexa obviamente importante para proxectar unha solución que instancia os artefactos correctamente, 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, o que ocorre cando a solución é retraído? 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.

Para axudar con iso, create a matrix that lists each artifact your solution deploys to SharePoint. List three columns per artifact, un para crear, actualizar e borrar. For each case, determinar o resultado correcto para que a operación.

This sort of analysis is obviously best done before the solution is ever deployed to a SharePoint farm. Con todo, como o tabaquismo, 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, pero polo menos vai ter colocar unha caixa en torno ao problema.

</final>

Rexístrate para o meu blog.

Siga-me no Twitter http://www.twitter.com/pagalvin