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

Bottom line, dit nie werk nie in WSS 3.0 (of MOSS).

Wanneer jy 'n berekende kolom, 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, dit vir jou vertel:

Een of meer kolom verwysings word nie toegelaat, omdat die kolomme word gedefinieer as 'n data tipe wat nie ondersteun word in formules.

Work Around: 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.

Nuttige skakels op berekende velde in die algemeen:

• Die gebruik van [Me] in 'n berekende kolom
• Voorbeelde van formule uitdrukkings (vergunning van http://jopx.blogspot.com/2007/10/calculated-fields-in-windows-sharepoint.html)

Vinnige disclaimer: Ek glo die bogenoemde om waar te wees en akkurate, maar ek het genoeg gesien slim truuks hier en daar in MOSS / WSS dat ek nie sou baie verbaas (nuuskierig as jy wil) 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, laat weet my asseblief!

We did some heavy duty re-organizing of our site taxonomy via "Manage Content and Structure". For reasons unknown to me, hierdie proses (al die werk in die belangrikste) broke some navigation links in the quick launch. The broken links are characterized by:

• Wrong URL. Byvoorbeeld, it should be "/sites/departments/HumanResources/…". Egter, the new link is "/sites/Corporate/HumanResources/…".
• Herhaal stukkies op die navraag string van die opskrif, soos in:

/terreine / departemente / human / _layouts / viewlsts.aspx?BaseType=0?BaseType=0?BaseType=0?BaseType=0

That’s easy enough to fix via site settings/navigation. Except, MOSS bied my met hierdie wanneer ek probeer en doen dit:

Die feit is, niemand is om enige verandering is daar (Afgesien van my, natuurlik).

'N vinnige soektog draai hierdie MSDN forums bespreking: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1691577&SiteID=1

William Heurdier lê dit uit mooi in die die voorlaaste (soos van 10/02/07) pos:

Feit is:

Korrupte opskrifte te herstel, jy het om te :

– verwyder al die lyste onder beskadig opskrif

– verwyder beskadig opskrif

– Uit die lys instellings, add a removed list to the quick launch (Dit herstel 'n nie beskadig opskrif)

Jy is dan goed om te gaan….

---

Sharepoint Expert – Cap Gemini Sogeti Switserland

Ek was 'n bietjie verward omdat ek wil om te gaan na die navigasie bladsy, make the change and then get hit with the "page was modified" message. Uiteindelik, 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!

</einde>

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

Agtergrond:

Ons het 'n besigheid vereiste waar 'n omgewing ingenieurswese bestuurder nodig het om te verseker dat 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 (of haar assistent.) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

Omgewing:

MOSS, 64 bietjie, virtuele masjien omgewing (ontwikkeling boks), 2 servers (SQL op bediener #1, alles op bediener #2).

Probleme:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. Egter, dit werk nie goed uit die boks (vir ons).

1. Die workflow taak is nie om te hardloop, ever. I discovered this by reading through Christopher White se (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:\>

   Dit was 'n verrassende uitslag, maar maklik opgelos:

   C:\>stsadm -o setproperty -propertyname "job-worfklow" -propertyvalue "every 1 minute tussen 0 en 59" -url http://localhost

   Operasie suksesvol voltooi.

   C:\>

   By dit te doen, the first "In Progress" workflow vinnig afgedank word en het dit se werk.

2. Ongelukkig, the next one didn’t work as expected. Gelukkig, Christopher refers us hier (http://support.microsoft.com/kb/932816). As of writing of this entry, ons wag vir die IT-afdeling te verkry dat die hotfix, but it does look promising. Our copies of the affected .dll’s do not share the same byte size, so hopelik sal dit die probleem op te los.

Work Around:

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

Vrae / Kwessies:

Stop Tot Datum werk nie.

Stop Tot Datum hervat nie.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"