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

Bottom line, nach bhfuil an obair i SSU 3.0 (nó CAONAIGH).

Nuair a chur colún ríomh, 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, Insíonn sé duit:

Ní amháin nó níos mó tagairtí colún Tá cead, mar go bhfuil sainmhínithe na colúin mar chineál sonraí ann nach dtacaítear leis i foirmlí.

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.

Naisc úsáideacha ar réimsí arna ríomh i gcoitinne:

• Ag baint úsáide as [Mise] i gcolún ríomh
• Samplaí de nathanna foirmle (caoinchead http://jopx.blogspot.com/2007/10/calculated-fields-in-windows-sharepoint.html)

Quick Fógra dlithiúil-séantóir: Creidim go bhfuil an thuas a bheith fíor agus cruinn, ach mé le feiceáil go leor cleasanna cliste anseo agus ansiúd sa MOSS / SSU go ní ba mhaith liom a bheith an-ionadh (agog más maith leat) 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, cuir in iúl dom!

We did some heavy duty re-organizing of our site taxonomy via "Manage Content and Structure". For reasons unknown to me, an bpróiseas seo (cé go obair sa phríomh-) broke some navigation links in the quick launch. The broken links are characterized by:

• Wrong URL. Mar shampla, it should be "/sites/departments/HumanResources/…". Mar sin féin, the new link is "/sites/Corporate/HumanResources/…".
• Giotán Arís agus arís eile ar an teaghrán cheist an cheannteidil, mar atá i:

/suímh / ranna / HumanResources / _layouts / viewlsts.aspx?BaseType=0?BaseType=0?BaseType=0?BaseType=0

That’s easy enough to fix via site settings/navigation. Except, MOSS i láthair liom leis seo nuair a thugaim agus é a dhéanamh:

Is é fírinne, Tá aon duine a dhéanamh ar aon athrú ann (leataobh ó dom, ar ndóigh).

A cuardach tapa casadh suas an fóraim phlé MSDN: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1691577&SiteID=1

William Heurdier leagann sé amach nicely sa leathdhéanach an (mar ar 10/02/07) phost:

Is fíric:

Chun a athshocrú ceannteidil truaillithe, caithfidh tú a :

– bhaint as na liostaí faoin gceannteideal truaillithe

– bain gceannteideal truaillithe

– Ón liosta suímh, add a removed list to the quick launch (Seo a athghiniúint neamh truaillithe ceannteideal)

Tá tú ansin go maith chun dul….

---

Sharepoint Saineolaithe – Cap Gemini Sogeti Eilvéis

Bhí mé beagán mearbhall mar gheall ar choinnigh mé ag iarraidh dul go dtí an leathanach nascleanúint, make the change and then get hit with the "page was modified" message. Faoi dheireadh, 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!

</deireadh>

Liostáil le mo bhlag!

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

Cúlra:

Tá riachtanas gnó nuair is gá bainisteoir innealtóireachta comhshaoil ​​a chinntiú go 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 (nó a cúnta) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

Comhshaol:

CAONAIGH, 64 giotán, timpeallacht meaisín fíorúil (bosca forbartha), 2 freastalaithe (SQL ar an bhfreastalaí #1, gach rud eile ar an bhfreastalaí #2).

Fadhbanna:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. Mar sin féin, ní oibríonn sé go maith as an bhosca (dúinn).

1. Ní raibh an post sreabhadh oibre sceidealta a reáchtáil, ever. I discovered this by reading through Christopher White (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" -moladh http://localhost

   <Property Exist="No" />

   C:\>

   Ba é sin de bharr iontas ach go héasca réiteach:

   C:\>stsadm -o setproperty -propertyname "job-worfklow" -propertyvalue "every 1 nóiméad idir 0 agus 59" -moladh http://localhost

   Oibríocht i gcrích go sásúil.

   C:\>

   Ar déanamh sin, the first "In Progress" sreabhadh oibre fired suas go tapa agus rinne sé post.

2. Faraor, the next one didn’t work as expected. Thankfully, Christopher refers us anseo (http://support.microsoft.com/kb/932816). As of writing of this entry, táimid ag fanacht leis an roinn TF sin a fháil hotfix, but it does look promising. Our copies of the affected .dll’s do not share the same byte size, mar sin tá súil againn go mbeidh sé seo an fhadhb a réiteach.

Workaround:

Re-running the stsadm -o setproperty command seemed to prod the workflow timer awake. It would, garbh 7 nóiméad ina dhiaidh sin, actually wake up and continue along with the workflow.

Ceisteanna / Ceisteanna Aghaidh:

Ní Sos Go dtí Dáta obair.

Ní Sos Go dtí Dáta atosú.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"