People commonly ask about using a column of data type "Person or Group" in another column of data type "Calculated".

Bottom line, isto non funciona en WSS 3.0 (ou Moss).

Engadindo unha columna calculada, WSS shows the list of fields it allows you to use for the calculation. If you type in the name of a column that is not in its list, dille:

Un ou máis referencias de columnas non son permitidas, por que as columnas son definidas como un tipo de datos que non é soportado en fórmulas.

Resolución: Use an event handler. The event handler fires when the user saves the item. It performs the update you would have wanted the calculated column to do for you.

Ligazóns útiles en campos calculados en xeral:

• Uso [Me] nunha columna calculada
• Exemplos de expresións de fórmula (cortesía de http://jopx.blogspot.com/2007/10/calculated-fields-in-windows-sharepoint.html)

AVISO LEGAL rápida: Eu creo que o anterior para ser certas e precisas, pero xa vin o suficiente trucos intelixentes aquí e alí en Moss / WSS que eu non sería moi sorprendido (curioso se quere) if someone has figured out a way to do this without resorting to code. If you’ve figured out clever work-around or know someone that did, por favor me aviso!

We did some heavy duty re-organizing of our site taxonomy via "Manage Content and Structure". For reasons unknown to me, este proceso (a pesar de traballar no esencial) broke some navigation links in the quick launch. The broken links are characterized by:

• Wrong URL. Por exemplo, it should be "/sites/departments/HumanResources/…". Con todo, the new link is "/sites/Corporate/HumanResources/…".
• Anacos repetido na secuencia de consulta do título, como no:

/locais / departamentos / HumanResources / _layouts / viewlsts.aspx?BaseType=0?BaseType=0?BaseType=0?BaseType=0

That’s easy enough to fix via site settings/navigation. Except, Moss me preséntase con iso cando eu tentar facelo:

O feito é, ninguén está a facer calquera modificación non (ademais de me, claro).

Unha rápida procura transfórmase este MSDN foros de debate: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1691577&SiteID=1

William Heurdier coloca-lo ben no penúltimo (a partir de 10/02/07) publicar:

Feito é:

Para restaurar títulos corrompidos, ten que :

– eliminar todas as roldas baixo corrupto título

– eliminar corrupto título

– A partir das definicións da lista, add a removed list to the quick launch (Este rexenerar un non corrupto título)

Está, entón, preparado para ir….

---

Sharepoint especialista – Cap Gemini Sogeti Suíza

Eu estaba un pouco confuso, porque eu seguía querendo ir á páxina de navegación, make the change and then get hit with the "page was modified" message. Eventualmente, I realized I had to go to the list settings and remove/add it to quick launch. That did the trick. Happy times are here again!

</final>

Rexístrate para o meu blog!

Actualización 12/10/07: Hotfix as described in MSDN KB929816 solved the problem for us mentioned below. Obtain the hotfix and then install on each server on the farm. Entón, sharepoint configuration utility on each server. Here is the MS Support link for that KB: http://support.microsoft.com/kb/932816.

Fondo:

We have a business requirement where an environmental engineering manager needs to ensure that 30 some-odd manufacturing locations located throughout the United States needs to ensure that those plants file for their various state-mandated permits in a timely fashion. One approach we’ve investigated leverages the "Pause Until Date" activity available to us via SharePoint Designer worfklow. The engineering manager (or her assistant) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

Environment:

Moss, 64 bocado, virtual machine environment (development box), 2 servers (SQL on server #1, everything else on server #2).

Problems:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. Con todo, it does not work well out of the box (for us).

1. The workflow job was not scheduled to run, ever. I discovered this by reading through Christopher White’s (http://chrissyblanco.blogspot.com/2007/06/issues-with-delay-activity-in-moss.html) excellent write-up by using stsadm thusly:
   

   C:\>stsadm -o getproperty -propertyname "job-workflow" -url http://localhost

   <Property Exist="No" />

   C:\>

   That was a surprising result but easily solved:

   C:\>stsadm -o setproperty -propertyname "job-worfklow" -propertyvalue "every 1 minutes between 0 e 59" -url http://localhost

   Operation completed successfully.

   C:\>

   Upon doing that, the first "In Progress" workflow quickly fired up and did it’s job.

2. Desafortunadamente, the next one didn’t work as expected. Agradecidamente, Christopher refers us aquí (http://support.microsoft.com/kb/932816). As of writing of this entry, we’re waiting for the IT department to obtain that hotfix, but it does look promising. Our copies of the affected .dll’s do not share the same byte size, so hopefully this will solve the problem.

Resolución:

Re-running the stsadm -o setproperty command seemed to prod the workflow timer awake. It would, roughly 7 minutes later, actually wake up and continue along with the workflow.

Questions / Issues Addressed:

Pause Until Date does not work.

Pause Until Date does not resume.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"