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"

Forbhreathnú

An iontráil seo cur síos ar cás-staidéar cur síos ar MRO iarbhír (Cothabháil, Deisiú agus Oibríochtaí) próiseas ceadaithe sreabhadh oibre i bhfeidhm i CAONAIGH.

Ní hé seo an plé follasach teicniúla, ach ina ionad sin feidhmíonn a chur ar fáil fíor-domhan sampla a léiríonn conas a bhuail an ardán MOSS gá fíor-domhan.

(Is é seo an iontráil tras phost idir http://paulgalvin.spaces.live.com agus http://blogs.conchango.com)

Cúlra

Bhí an chliaint próiseas MRO arb iad is sainairíonna an méid seo a leanas

• Próiseas ceadaithe Lámhleabhar.
• Roinnt tacaíocht ag baint úsáide as scarbhileoga Excel.
• Irregular approval process. The same MRO purchase approval process would vary day to day, duine ag duine.
• Go leor de na páipéir agus sínithe lámhscríofa — foréilimh cheannaigh, a cheanglaítear suas go dtí 3 sínithe i scríbhinn roimh faomhadh deiridh.

Ní féidir cuspóirí an togra san áireamh:

• Fully uathoibriú na bpróiseas.
• Caighdeáin fiontraíochta le faomhadh a fhorfheidhmiú.
• Sholáthar dearcadh comhdhlúite de MRO cheannach do bhainisteoirí éagsúla.
• Detailed audit trail.

As a side effect of the solution, Bhí sínithe scríofa ag teastáil a thuilleadh.

Próiseas Faomhadh

The approval process consists of four "swim lanes": Tionscnóir, Bainisteoir Díreach, Bainisteoir Feidhme agus bainisteoir roinn.

Tionscnóir:

Sees the need for the purchase and starts the process. Note that the originator may or may not actually enter the purchase requisition, but instead direct another staff member to do so. Roinnt uaireanta, the originator does not have the technical expertise to fill out the PO requisition. Mar shampla, D'fhéadfadh d'úsáideoir ag iarraidh a fhoréileamh ar ríomhaire glúine nua, ach nach bhfuil a fhios an díoltóir is fearr, Caighdeáin TF, etc. Sa chás seo, the originator works with IT and IT actually fills out the requisition.

Bainisteoir Díreach:

Is é seo an bainisteoir díreach an tionscnóra (d'fhéadfadh a bheith difriúil ón duine a chuaigh i ndáiríre an foréileamh uimhir i CAONAIGH). Direct managers must approve the PO requisition before the system seeks approval further down the line.

Bainisteoir Feidhmeach:

The functional manager is the individual responsible for ensuring that the proposed purchase conforms to enterprise standards within the scope of a particular corporate function. Mar shampla, IT purchases are approved by an IT functional manager.

Bainisteoir Rannóige:

Division managers approve purchase requisitions strictly by dollar amount. Division manager approve purchase requisitions in excess of a configurable dollar amount.

An Réiteach

We used the following tools and components to implement the solution:

CAONAIGH: Serves as the platform off which everything else "hangs". MOSS provides bedrock services for security, máistir sonraí, rianta iniúchta agus gnéithe eile.

Foirmeacha InfoPath Seirbhísí: A chomhpháirt CAONAIGH, seo ar chumas úsáideoirí a líonadh amach foréilimh a cheannach trí bhrabhsálaí gréasáin.

SharePoint Dearthóir (SPD): Úsáid againn SPD a chur i bhfeidhm ar an bpróiseas sreabhadh oibre uathoibrithe.

Seirbhís Gréasáin: A c# web service enhances the user experience by enabling cascading selections lists in the InfoPath form and provides better performance with respect to filtering data. Féach anseo do Léim domhain teicniúil ar an ábhar seo agus na fáthanna atá againn a úsáid.

Liostaí Saincheaptha: MOSS user profiles provided a given user’s direct manager, but did not provide most of the data that controlled workflow decisions (e.g. cibé an bhfuil an bainisteoir rannáin gá a cheadú don fhoréileamh uimhir). We used custom lists in an "Enterprise Data" site to maintain data such as "Divisional Manager Approval Dollar Amount", "Functional Area Manager" and so forth. Lists integrated very nicely with InfoPath and also provide create/update/delete (CRUD) feidhmiúlacht na gcaighdeán iniúchta agus amach as slándáil an bosca.

Bain úsáid as Cás

Léiríonn an cás seo a úsáid conas a oireann an réiteach le chéile:

1. Paul wants a new laptop. He describes his needs to Vivek, duine IT eolach ar na caighdeáin ríomhaire glúine corparáideach, díoltóirí is fearr, etc.
2. Logs Vivek i CAONAIGH, accesses the PO Requisition form and enters the requisition on behalf of Paul. The form prompts Vivek for a purchase category which then uses the web services to populate a drop-down list of company-approved vendors. Vivek also specifies the corporate functional area of this purchase (e.g. "IT" or "Finance").
3. Tosaíonn sreabhadh oibre bunaithe SPD, bainisteoir agus bealaí an ceanglas a bhainisteoir díreach chinnfidh Pól, Stacy.
4. Stacy fhormheasann an foréileamh a cheannach.
5. SPD workflow inspects the requisition and determines it’s an IT purchase. It routes the workflow to the IT functional manager, Wonson.
6. Wonson fhormheasann an foréileamh.
7. SPD sreabhadh oibre iniúchadh arís an fhoréilimh agus go gcinnfidh gur mó an méid a cheannach le méid Dollar Maxium agus bealaí do bhainisteoir rannán ar cheadú.
8. Ceadaíonn an bainisteoir roinn an foréileamh a cheannach.

Nótaí

• The use case demonstrates a "clean" run with no rejections or jumps.
• Every approver has the ability to approve or reject the requisition as well as provide written comments. These are logged in the audit trail.
• Má dhiúltaíonn bainisteoir freagrach an foréileamh a cheannach ag aon phointe, the PO requisition is "dead" and the process must be started from the beginning.
• Sreabhadh oibre in iúl don tionscnóir ag gach céim den phróiseas.
• Uimh sínithe scríofa — an cliant a chinnfear (tar éis roinnt moltaí forceful) go bhfuil an rian iniúchóireachta mar a sholáthraítear trí mheán a stair sreabhadh oibre, sheirbheáil riachtanais a n-iniúchta.
• Iarracht — it took approximately three man weeks to implement this solution.

Conclúid

This solution leverages MOSS as a development and run-time platform. The client was able to leverage core MOSS features to automate a routine business process that affected nearly every employee in the company. With the exception of a simple web service (a ghiaráil féin CAONAIGH), almost no actual "programming" bhí gá le.

The solution also serves as a "showcase" don chliant, demonstrating how different MOSS features can be combined to create a fully featured business application and generate new consulting opportunities in the future.

Gluais

MRO: Cothabháil, repair and operations. These purchases typically include items such as notepads, cathaoireacha, ríomhairí pearsanta, printéirí, teileafóin phóca agus a leithéidí.

D'fhéadfadh sé seo a bheith soiléir go leor, ach iad ag staidéar do mo scrúdú cláir MOSS, D'fhoghlaim mé go bhfuil sé éasca go leor a fháil ar an XML iarbhír ó cheist chuardaigh tríd an comhéadan úsáideora.

Is modh amháin tapaidh mar seo a leanas:

• Rochtain cuardach casta.
• Cuardach a dhéanamh go bhfilleann cuid de na sonraí.
• Cuir an leathanach (trí suímh láithreán).
• Athraigh an XSL seo a leanas:

<?xml leagan="1.0" ionchódú="utf-8"?>
<XSL:Stílbhileog leagan="1.0" xmlns:XSL="http://www.w3.org/1999/XSL/Transform">
<XSL:aschur modh="xml" leagan="1.0" ionchódú="UTF-8" fleasc="yes"/>
<XSL:teimpléad mheaitseáil="/">
<réamh>
<XSL:cóip de- roghnú="*"/>
</réamh>
</XSL:teimpléad>
</XSL:Stílbhileog>

• Buail isteach.
• Féach ar Foinse sa bhrabhsálaí.

Tabhair faoi deara go bhfuil an <réamh> tag doesn’t do much except serve as a convenient marker when you view the results.

This trick can be very helpful when working with managed properties and customizing search. It will provide a definitive list of the XML available for you to use in your xslt which would have been very helpful the last 25 amanna chruthaigh mé roinnt torthaí cuardaigh saincheaptha.

Ba chóir é seo a bheith ag obair le haghaidh dataviews chomh maith, cé nach bhfuil mé tástáil go amach go fóill.

Feicim go Eric Kraus was faced with a requirement normally met with a content query web part. An fhadhb? He was in a pure WSS environment with no access to the CQWP. Rather than curling up in the fetal position (a áiteamh go bhfuil mé le dul i ngleic gach lá, Dealraíonn sé), he came up with solution that at least gives WSS shops a fighting chance to succeed. It’s described anseo.

Stefan GOSSNER has put together a terrific 4-part series on the SharePoint Content and Deployment API anseo. It offers a great overview and very good examples in code (C #).

Phioc mé an chéad suas an nasc seo ó Joris poelmans bhlag ag http://jopx.blogspot.com/.

Fiú má tá tú cosúil liomsa, sa mhéid is nach bhfuil tú go raibh a dhéanamh i bhfad idir lámha ar an obair le haghaidh bainistíochta inneachair, tá sé seo fiú go maith 20 minutes of your time to read.

Ag baint úsáide as an API, féidir le duine:

• Onnmhairiú agus a allmhairiú ábhar an-éasca.
• Re-parent content. If you want to export some content from a site "A" and send it to site "B" ach in áit go hiomlán nua san ordlathas, seo agus is féidir.
• Ábhar Easpórtáil ó láithreán A agus allmhairiú giotán roghnaithe isteach site A.
• Ábhar Re-nasc (rud a chiallaíonn déileáil leis na hipearnasc).

Someone on the Internets was asking about how to create a calculated column on a list that would show a value formatted as "[Úsáideoir] – [Stádas] – [Suíomh]" as in "Paul Galvin – Óil [saor in aisce] Beoir – The Beach".

Paul would go in and update his entry in the list and the calculated column would update appropriately. The [Úsáideoir] Ba chóir réamhshocraithe don úsáideoir dul isteach / thabhairt cothrom le dáta an liosta an.

A calculated column cannot use "volatile" feidhmeanna mar [Mise] nó [Sa lá atá inniu]. I solved it in a test environment with these steps:

1. Create a text column named "Current User".
2. Socraigh a luach réamhshocraithe a [Mise]
3. Create a calculated column called "Calc Test".
4. Socraigh a luach; [Úsáideoir Reatha]

Chuaigh mé i, Chuir mhír chun an liosta agus d'oibrigh sé.

Tá mé ag plagued le seo ar feadh 9 féach mhí agus go bhfuil daoine ar an MSDN agus fóraim Usenet too.l sé

Uaireanta, nuair a rochtain a fháil ar dhoiciméad focal (nó cineálacha doc eile) ó leabharlann doiciméad cúiseanna Internet Explorer a tuairteála go simplí agus dul amach (ag cur na tabs leis má tá aon oscailt).

D'fhéadfadh sé seo hotfix MS réiteach é: http://support.microsoft.com/kb/938888

Chomh maith leis sin, níl roinnt cur síos mar gheall ar an fhadhb anseo:

http://jopx.blogspot.com/2007/07/solving-internet-explorer-crash-when.html

Forbhreathnú:

Cruthaithe liosta saincheaptha a bhainistíonn le cineál ábhar le roinnt colún dosaen.

Curtha sé le leathanach agus ina dhiaidh sin trí SPD, thiontú d'fhonn sonraí.

Fadhb:

My Xpath expression was returning blank for a column named "Current Position". I referenced it thusly:

    <table border="1">
      <XSL:for-each select="/dsQueryResponse/Rows/Row" >
        <tr>
          <td>
            Stádas Reatha:
            <XSL:value-of select="@Current_x0020_Status"></XSL:luach-ar>
          </td>
        </tr>
      </XSL>
    </tábla>

The column in the CT is named "Current Status". It shows up in the lookup as "Current Status". Everywhere you look, you see "Current Status".

Cé thrashing madly faoi, lorg ar réiteach, I instead referred to "@Recruiter" agus behold! — that actually returned back the current status. I expected it to return back the recruiter when I did that.

Réiteach:

I poked about in SPD. Go to that page in SPD and it shows the data view. You can inspect the actual data provided to the view and associated Xpath. Here I found out that indeed, the Xpath pointed at "Recruiter". Strangely enough, the "actual" recruiter field pointed from "Recruiter1".

Tóg Away:

SPD Soláthraíonn habairtí XPath údarásach do sraitheanna & colúin i d'fhonn sonraí.

Dara, it shows the actual data. So for example, Léiríonn colún den chineál seo:

<nobr><réise><A HREF="/sites/Corporate/HumanResources/TalentAcquisition/_layouts/userdisp.aspx?ID=17">Galvin, Paul</A><img = teorann"0" height="1" width="3" src="/_layouts/images/blank.gif"/><a href = 'javascript:’ onclick = 'IMNImageOnClick();tuairisceán bréige;’ aicme = "ms-imnlink '><img name=’imnmark’ title =” teorann =’0′ airde = '12’ width = '12’ src = "/ _layouts / images / blank.gif’ Poiblı = 'Níl aon eolas láithreacht’ PGalvin@xxx.com sip = '’ id = 'imn_77, type = SMTP' /></a></réise></nobr>