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

Imo linea, hoc non operetur in WSS 3.0 (vel MUSCUS).

Cum addita ratione agmen, 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, Is dico vos:

Unus vel plures columns References non liceat, quia non est modus columnae datis sustineantur definitur formulae.

Workaround: 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.

Suspendisse in ratione communi in agris:

• Usura [Me] in columna iniri
• Exempla formularum expressiones (Affabilitatem http://jopx.blogspot.com/2007/10/calculated-fields-in-windows-sharepoint.html)

Lorem vivos: Et illa vera et accurata, sed vidi tantum passim ingeniis musco / WSS ut non mirum sit amet (Sin ATTONITUS) 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, placet me cognoscere!

We did some heavy duty re-organizing of our site taxonomy via "Manage Content and Structure". For reasons unknown to me, hoc processus (quamquam in summa operantes) broke some navigation links in the quick launch. The broken links are characterized by:

• Wrong URL. Verbigratia, it should be "/sites/departments/HumanResources/…". Autem, the new link is "/sites/Corporate/HumanResources/…".
• Repetitur frenos in titulo quaestionis filum, ut in:

/sites / Dicasteria / HumanResources / _layouts / viewlsts.aspx?BaseType = 0?BaseType = 0?BaseType = 0?BaseType = 0

That’s easy enough to fix via site settings/navigation. Except, MUSCUS sistit hic me experior me et faciam illud:

Hoc est,, Nemo ulla mutatione (declinavimus a me, utique).

A vivos quaerere irrepserit hac forums Discussion MSDN: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1691577&SiteID=1

Willelmi Belle Heurdier posuerit eam in penultima (tamquam 10/02/07) stipes:

Hoc est,:

Corrupta ad reset headings, habes :

– omnem tabularum sub capite corrupto

– aufero caput capitis corrumpi

– A occasus album, add a removed list to the quick launch (Haec non corrumpuntur petenti regenerare)

Vos igitur ad bonum….

---

Peritus Sharepoint – Cap Sogeti Gemini Helvetia

Confusus sum, quia ego, volens transire amet consectetuer navigatio, make the change and then get hit with the "page was modified" message. Tandem, 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!

</finem>

Scribet ad mea blog!

UPDATE 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. Igitur, sharepoint configuration utility on each server. Here is the MS Support link for that KB: http://support.microsoft.com/kb/932816.

Background:

An environmental engineering amet habemus negotium ubi necessitas requirit ut 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 (vel eius vicarii) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

Environment:

MUSCUS, 64 frenum, Rectum Apparatus environment (progressionem buxum), 2 servientibus (In SQL servo #1, omnia alia server #2).

Problemata:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. Autem, Quisque a quam non faciat (pro nobis).

1. Job non workflow est scheduled ad currere, ever. I discovered this by reading through CHRISTOPHORVS Albus scriptor (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:\>

   Quod mirum erat, sed facile solvitur per:

   C:\>stsadm -o setproperty -propertyname "job-worfklow" -propertyvalue "every 1 inter minutes 0 et LIX" -url http://localhost

   Operatio feliciter expletum.

   C:\>

   Quod faciendum, the first "In Progress" workflow celeriter officium fecit et concitus.

2. Miserabile, the next one didn’t work as expected. Gratanter, Christopher refers us hic (http://support.microsoft.com/kb/932816). As of writing of this entry, IT department sumus expectantes obtinere hotfix, but it does look promising. Our copies of the affected .dll’s do not share the same byte size, ita spero satisfaciet proposito.

Workaround:

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

Quæstiones / Alloquitur exitibus:

Donec mora Date non operatur.

Date mora Donec non recuperabit.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"