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

Bottom line, kjo nuk do të punojnë në WSS 3.0 (ose MOSS).

Kur duke shtuar një kolonë llogaritur, 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, ajo ju tregon:

Një ose më shumë referenca kolonë nuk janë të lejuara, sepse shtyllat janë të përkufizohet si një lloj të të dhënave që nuk është i mbështetur në formulat.

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.

Lidhje të dobishme në fusha të llogaritura në përgjithësi:

• Përdorim [Mua] në një kolonë llogaritur
• Shembuj të shprehjeve formulë (mirësjellje e http://jopx.blogspot.com/2007/10/calculated-fields-in-windows-sharepoint.html)

Mohim i shpejtë: Unë besoj se më lart që të jetë e vërtetë dhe e saktë, por unë kam parë mjaft truket zgjuar këtu dhe atje në MOSS / WSS se unë nuk do të jetë i befasuar shumë (etur në qoftë se ju do të) 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, ky proces (pse punon në kryesore) broke some navigation links in the quick launch. The broken links are characterized by:

• Wrong URL. Për shembull, it should be "/sites/departments/HumanResources/…". Megjithatë, the new link is "/sites/Corporate/HumanResources/…".
• Bit e përsëritura në vargun pyetës të kreut, si në:

/faqet / departamentet / HumanResources / _layouts / viewlsts.aspx?BaseType = 0?BaseType = 0?BaseType = 0?BaseType = 0

That’s easy enough to fix via site settings/navigation. Except, MOSS prezanton mua me këtë, kur unë të përpiqet dhe të bëjë atë:

Fakti është, askush nuk është duke bërë ndonjë ndryshim atje (mënjanë prej meje, sigurisht).

Një kërkim të shpejtë kthehet deri këtë diskutim Forume MSDN: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1691577&SiteID=1

William Heurdier paraqet atë bukur në parafundit (si i 10/02/07) post:

Fakti është:

Për të rivendosur titujt korruptuar, ju keni për të :

– hequr të gjitha listat nën titullin korruptuar

– hiqni korruptuar nisej

– Nga cilësimet e listës, add a removed list to the quick launch (Kjo rigjenerohet një titull jo i korruptuar)

Atëherë ju jeni të mirë për të shkuar….

---

SharePoint Ekspert – Sogeti Cap Gemini Zvicer

Unë kam qenë pak i hutuar, sepse kam mbajtur që dëshirojnë për të shkuar tek faqja e navigimit, make the change and then get hit with the "page was modified" message. Eventually, 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!

</fund>

Abonohen në blogun tim!

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

Sfond:

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 bit, 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. Megjithatë, 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 minuta në mes të 0 dhe 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. Mjerisht, the next one didn’t work as expected. Fatmirësisht, Christopher refers us këtu (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.

Workaround:

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"