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

Bottom line, hii haina kazi katika WSS 3.0 (au MOSS).

Wakati kuongeza safu ya mahesabu, 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, ni atakwambia:

Marejeo safu moja au zaidi hawaruhusiwi, kwa sababu nguzo hufafanuliwa kama aina data kwamba si mkono katika formula.

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.

Muhimu viungo kwenye mashamba mahesabu kwa ujumla:

• Kutumia [Mimi] katika safu ya mahesabu
• Mifano ya maneno formula (hisani ya http://jopx.blogspot.com/2007/10/calculated-fields-in-windows-sharepoint.html)

Haraka Kanusho: Naamini hapo juu kuwa ni kweli na sahihi, lakini nimeona tricks wajanja kutosha hapa na pale katika MOSS / WSS kwamba mimi bila kuwa na kushangazwa sana (agog kama wewe) 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, tafadhali napenda kujua!

We did some heavy duty re-organizing of our site taxonomy via "Manage Content and Structure". For reasons unknown to me, mchakato huu (ingawa kazi katika kuu) broke some navigation links in the quick launch. The broken links are characterized by:

• Wrong URL. Kwa mfano, it should be "/sites/departments/HumanResources/…". Hata hivyo, the new link is "/sites/Corporate/HumanResources/…".
• Mara kwa mara bits juu ya kamba swala ya viongozi, kama katika:

/maeneo / idara / HumanResources / _layouts / viewlsts.aspx?BaseType=0?BaseType=0?BaseType=0?BaseType=0

That’s easy enough to fix via site settings/navigation. Except, MOSS inatoa yangu kwa hii wakati mimi kujaribu na kufanya hivyo:

Ukweli ni, hakuna mtu ni kufanya mabadiliko yoyote kuna (kando kutoka kwangu, bila shaka).

kutafuta haraka zamu up hii MSDN ukumbi wa majadiliano: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1691577&SiteID=1

William Heurdier anajaalia ni nje nicely katika iliyokaribia mwisho (kama ya 10/02/07) baada ya:

Ukweli ni:

Upya vichwa kupotoshwa, una :

– kuondoa orodha zote chini ya kichwa kupotoshwa

– kuondoa kupotoshwa viongozi

– Kutoka kwa mazingira orodha, add a removed list to the quick launch (Hii regenerate si kupotoshwa viongozi)

Wewe ni basi nzuri ya kwenda….

---

Sharepoint Mtaalam – Sura Gemini Sogeti Uswisi

Nilikuwa kidogo kuchanganyikiwa kwa sababu mimi naendelea kutaka kwenda ukurasa urambazaji, make the change and then get hit with the "page was modified" message. Hatimaye, 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!

</mwisho>

Kujiunga na blog yangu!

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

Background:

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. Hata hivyo, 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 and 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. Cha kusikitisha, the next one didn’t work as expected. Nashiriki, Christopher refers us hapa (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.

Maswali / 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"