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

Neðsta lína, þetta virkar ekki í WSS 3.0 (eða Moss).

Þegar að bæta við reiknað dálk, 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, it tells you:

One or more column references are not allowed, because the columns are defined as a data type that is not supported in formulas.

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

Useful links on calculated fields in general:

• Notkun [Mig] í reiknað dálki
• Examples of formula expressions (courtesy of http://jopx.blogspot.com/2007/10/calculated-fields-in-windows-sharepoint.html)

Quick disclaimer: I believe the above to be true and accurate, but I’ve seen enough clever tricks here and there in MOSS/WSS that I wouldn’t be extremely surprised (agog if you will) 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, please let me know!

We did some heavy duty re-organizing of our site taxonomy via "Manage Content and Structure". For reasons unknown to me, þetta ferli (þó að vinna í helstu) broke some navigation links in the quick launch. The broken links are characterized by:

• Wrong URL. Til dæmis, it should be "/sites/departments/HumanResources/…". Hins, the new link is "/sites/Corporate/HumanResources/…".
• Endurtekin bitar á fyrirspurninni band af fyrirsögninni, eins og í:

/staður / deildir / HumanResources / _layouts / viewlsts.aspx?BaseType=0?BaseType=0?BaseType=0?BaseType=0

That’s easy enough to fix via site settings/navigation. Except, MOSS kynnir mig með þetta þegar ég reyna að gera það:

Staðreyndin er, enginn er að gera allar breytingar þar (innskot frá mér, auðvitað).

A fljótur leita snýr upp þessa MSDN umræður: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1691577&SiteID=1

William Heurdier setur það út fallega í penultimate (og með 10/02/07) staða:

Staðreyndin er:

Til að núllstilla skemmd fyrirsagnir, þú þarft að :

– fjarlægja allar skrár undir skemmd lið

– fjarlægja skemmd stefnir

– Af listanum stillingum, add a removed list to the quick launch (Þetta endurfæða a non skemmd stefnir)

Þú ert þá gott að fara….

---

Sharepoint Expert – Cap Gemini Sogeti Sviss

Ég var dálítið ruglaður af því að ég hélt að vilja fara á flakk síðuna, make the change and then get hit with the "page was modified" message. Lokum, 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!

</enda>

Gerast áskrifandi að bloggið mitt!

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

Bakgrunnur:

Við hafa a viðskipti kröfu þar umhverfis verkfræði framkvæmdastjóri þarf að tryggja að 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 (eða aðstoðarmaður hennar) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

Umhverfi:

Moss, 64 hluti, raunverulegur vél umhverfi (þróun kassi), 2 netþjónum (SQL á vefþjóninum #1, allt annað á þjóninum #2).

Vandamál:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. Hins, það virkar ekki vel út af the kassi (fyrir okkur).

1. The workflow starf var ekki áætlað að keyra, ever. I discovered this by reading through Christopher er hvítur (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:\>

   Það var óvart vegna en auðveldlega leyst:

   C:\>stsadm -o setproperty -propertyname "job-worfklow" -propertyvalue "every 1 mínútur á milli 0 og 59" -url HTTP://localhost

   Aðgerð lokið.

   C:\>

   Þegar aðgerð sem, the first "In Progress" workflow rekinn fljótt upp og gerði það starf.

2. Því miður, the next one didn’t work as expected. Sem betur fer, Christopher refers us hér (http://support.microsoft.com/kb/932816). As of writing of this entry, við erum að bíða eftir að IT deild til að fá að snarhasti, but it does look promising. Our copies of the affected .dll’s do not share the same byte size, svo vonandi mun þetta leysa vandamál.

Lausn:

Re-running the stsadm -o setproperty command seemed to prod the workflow timer awake. It would, u.þ.b. 7 mínútum síðar, actually wake up and continue along with the workflow.

Spurningar / Mála sem:

Hlé þar til dagsetning virkar ekki.

Hlé þar til dagsetning ekki aftur.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"