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

Bottom line, dan ma taħdimx fl WSS 3.0 (jew MOSS).

Meta tiżdied kolonna kkalkulata, 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, hija jgħidlek:

Wieħed jew aktar referenzi kolonna mhumiex permessi, minħabba li l-kolonni huma definiti bħala tip ta 'data li mhijiex appoġġjata fil-formuli.

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.

Links utli dwar oqsma kkalkulati b'mod ġenerali:

• Jużaw [Me] fil-kolonna kkalkulata
• Eżempji ta 'espressjonijiet formula (korteżija ta ' http://jopx.blogspot.com/2007/10/calculated-fields-in-windows-sharepoint.html)

Quick disclaimer: Nemmen li l-hawn fuq biex ikunu vera u preċiża, imma stajt tidher tricks għaqlija biżżejjed hawn u hemm fil MOSS / WSS li jien mhux se jkun estremament sorpriż (agog jekk inti se) 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, jekk jogħġbok let me know!

We did some heavy duty re-organizing of our site taxonomy via "Manage Content and Structure". For reasons unknown to me, dan il-proċess (għalkemm jaħdmu fil-prinċipali) broke some navigation links in the quick launch. The broken links are characterized by:

• Wrong URL. Per eżempju, it should be "/sites/departments/HumanResources/…". Madankollu, the new link is "/sites/Corporate/HumanResources/…".
• Ripetuti bits fuq il-sekwenza mistoqsija tal-intestatura, kif fil-:

/siti / dipartimenti / HumanResources / _layouts / viewlsts.aspx?BaseType = 0?BaseType = 0?BaseType = 0?BaseType = 0

That’s easy enough to fix via site settings/navigation. Except, MOSS jippreżenta lili ma dan meta I tipprova tagħmel dan:

Il-fatt hu, ebda waħda qed tagħmel kull bidla hemm (apparti minn me, tal-kors).

A quick tfittxija dawriet up dan forums diskussjoni MSDN: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1691577&SiteID=1

William Heurdier jistipula out nicely fil-l ta 'qabel (bħala ta ' 10/02/07) post:

Fatt huwa:

Għal reset intestaturi korrotta, inti għandek :

– tneħħi l-listi taħt l-intestatura korrotta

– neħħi korrotta intestatura

– Mill-issettjar lista, add a removed list to the quick launch (Dan riġenerat intestatura non korrotta)

Inti mbagħad tajba biex tmur….

---

Sharepoint Espert – Sogeti Cap Gemini Isvizzera

I kien daqsxejn konfuż minħabba I tinżamm jixtiequ li jmorru għall-paġna ta 'navigazzjoni, make the change and then get hit with the "page was modified" message. Eventwalment, 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!

</aħħar>

Abbona għall-blog tiegħi!

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

Sfond:

Għandna rekwiżit tan-negozju fejn manager inġinerija ambjent jeħtieġ li tiżgura li 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 (jew assistent tagħha) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

Ambjent:

MOSS, 64 bit, ambjent magna virtwali (kaxxa iżvilupp), 2 servers (SQL fuq server #1, kull ħaġa oħra fuq server #2).

Problemi:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. Madankollu, ma jaħdimx sew barra mill-kaxxa (għalina).

1. Ix-xogħol workflow kienx skedat jiddekorri, ever. I discovered this by reading through Christopher White Paper (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:\>

   Dan kien riżultat sorprendenti imma jissolvew faċilment:

   C:\>stsadm -o setproperty -propertyname "job-worfklow" -propertyvalue "every 1 minuta bejn 0 u 59" -url http://localhost

   Operazzjoni kompluta b'suċċess.

   C:\>

   Malli tagħmel dan, the first "In Progress" workflow malajr fired up u ma impjieg huwa.

2. Sfortunatament, the next one didn’t work as expected. Thankfully, Christopher refers us hawn (http://support.microsoft.com/kb/932816). As of writing of this entry, aħna qed jistennew għall-dipartiment IT sabiex tikseb dan hotfix, but it does look promising. Our copies of the affected .dll’s do not share the same byte size, hekk nisperaw li dan se ssolvi l-problema.

Workaround:

Re-running the stsadm -o setproperty command seemed to prod the workflow timer awake. It would, bejn wieħed u ieħor 7 minuti wara, actually wake up and continue along with the workflow.

Mistoqsijiet / Kwistjonijiet indirizzati:

Pause Sa Data ma taħdimx.

Pause Sa Data ma jerġa 'jibda.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"