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"

Ħarsa ġenerali

Din l-entrata jiddeskrivi studju ta 'każ li jiddeskrivi MRO attwali (Manutenzjoni, Tiswija u Operazzjonijiet) proċess ta 'approvazzjoni workflow implimentat MOSS.

Dan mhuwiex diskussjoni overtly tekniku, iżda minflok iservi biex jipprovdi eżempju tad-dinja reali li turi kif il-pjattaforma MOSS sabiex jissodisfaw bżonnijiet tad-dinja reali.

(Din l-entrata hija taqsam stazzjonati bejn http://paulgalvin.spaces.live.com u http://blogs.conchango.com)

Sfond

Proċess MRO tal-klijent kien ikkaratterizzat minn dan li ġej

• Proċess ta 'approvazzjoni manwali.
• Xi appoġġ tuża teċċellax spreadsheets.
• Proċess ta 'approvazzjoni irregolari. L-istess proċess ta 'approvazzjoni xiri MRO ivarja jum għal jum, persuna minn persuna.
• Lottijiet ta 'karta u l-firem miktubin bl-idejn — xiri requisitions meħtieġa sa 3 firem miktuba qabel l-approvazzjoni finali.

L-għanijiet ta 'dan il-proġett inkluda:

• Bis-sħiħ awtomat-proċess.
• Jinfurzaw l-istandards impriżi għall-approvazzjoni.
• Ipprovdi ħarsa ġenerali konsolidata tas MRO xiri għal amministraturi diversi.
• Rekord ta 'verifika dettaljata.

Bħala effett sekondarju tas-soluzzjoni, firem bil-miktub ġew m'għadhiex meħtieġa.

Proċess approvazzjoni

Il-proċess ta 'approvazzjoni jikkonsisti f'erba' "jgħum korsiji": Oriġinatur, Manager Direct, Manager funzjonali u maniġer diviżjoni.

Oriġinatur:

Jara l-ħtieġa għax-xiri u jibda l-proċess. Innota li l-oriġinatur jistgħu jew ma jistgħux attwalment jidħlu fil-rekwiżizzjoni xiri, iżda minflok dirett membru tal-persunal oħra tagħmel dan. Some times, l-oriġinatur ma jkollux il-kompetenza teknika biex jimla l-rekwiżizzjoni PO. Per eżempju, utent tista 'tixtieq li rekwiżizzjoni' kompjuter laptop ġdid, iżda ma tkunx taf l-bejjiegħ aħjar, IT standards, eċċ. F'dan il-każ, min joriġina jaħdem ma 'l-IT u l-IT fil-fatt jimla l rekwisizzjoni.

Manager Direct:

Dan huwa l-maniġer dirett ta 'l-oriġinatur (li tista 'tkun differenti mill-persuna li attwalment daħlu fil-rekwiżizzjoni PO fis MOSS). Managers diretti għandhom japprovaw l-rekwiżizzjoni PO quddiem is-sistema ifittex approvazzjoni aktar 'l isfel il-linja.

Funzjonali Manager:

Il-maniġer funzjonali hija l-individwu responsabbli għall-iżgurar li x-xiri propost jikkonforma mal-istandards intrapriża fl-ambitu ta 'funzjoni korporattiva partikolari. Per eżempju, Xiri IT huma approvati minn maniġer funzjonali IT.

Diviżjoni Manager:

Maniġers diviżjoni japprova xiri requisitions strettament b'ammont dollaru. Maniġer diviżjoni japprova requisitions xiri f'eċċess ta 'ammont ta' dollari configurable.

Il-Soluzzjoni

Aħna użati l-għodod u l-komponenti li ġejjin biex jimplimenta s-soluzzjoni:

MOSS: Sservi bħala l-pjattaforma off li kull ħaġa oħra "prekarja". MOSS tipprovdi servizzi sodda tal-blat għas-sigurtà, data kaptan, sekwenzi ta 'verifika u fatturi oħra.

InfoPath jifforma servizzi: A komponent MOSS, dan jippermetti lill-utenti biex jimla xiri requisitions permezz ta 'web browser.

SharePoint Designer (SPD): Aħna użati SPD biex jimplimentaw il-proċess workflow awtomatizzati.

Web Service: A servizz c # web ttejjeb l-esperjenza utent billi tippermetti cascading listi selezzjonijiet fil-forma InfoPath u jipprovdi rendiment aħjar fir-rigward tad-data filtrazzjoni. Ara hawn għal adsa fond tekniku dwar dan is-suġġett u r-raġunijiet tagħna għall-użu tiegħu.

Listi Custom: Profili utent MOSS sakemm manager dirett utent partikolari s, iżda ma pprovdiex ħafna mill-informazzjoni li ikkontrollati deċiżjonijiet fluss tax-xogħol (e.g. jekk il-maniġer diviżjonali huwa meħtieġ li tapprova l-PO rekwiżizzjoni). Aħna użati listi dwana fi "Intrapriża Data" sit li jżommu d-data bħal "Ammont Dollar Diviżjonali Manager Approvazzjoni", "Funzjonali Manager Żona" u oħrajn. Listi integrati ħafna nicely mal InfoPath u wkoll jipprovdu joħolqu / aġġornament / iħassru (Crud) funzjonalità mal-verifika u l-sigurtà tal-kaxxa.

Użu Kawża

Dan il-każ l-użu turi kif is-soluzzjoni toqgħod flimkien:

1. Paul trid laptop ġdid. Huwa jiddeskrivi l-bżonnijiet tiegħu biex Vivek, persuna IT familjari ma 'standards korporattivi laptop, Preferred Bejjiegħa, eċċ.
2. Vivek zkuk fis MOSS, aċċessi l-forma PO Requisition u jidħol fil-rekwiżizzjoni f'isem Paul. Il-forma iqajjem Vivek għal kategorija xiri li mbagħad juża s-servizzi tal-web biex timla lista drop-down ta 'bejjiegħa approvati għat-kumpannija. Vivek jispeċifika wkoll il-qasam funzjonali korporattiva ta 'dan ix-xiri (e.g. "IT" jew "finanzjament").
3. SPD workflow bbażati jibda, manager u rotot l-rekwiżizzjoni li maniġer tiegħu diretta jiddetermina Pawl, Stacy.
4. Stacy japprova l-rekwiżizzjoni xiri.
5. Workflow SPD jispezzjona l rekwiżizzjoni u jiddetermina huwa ta 'xiri IT. Hija rotot l workflow għall-maniġer funzjonali IT, Wonson.
6. Wonson japprova l-rekwiżizzjoni.
7. SPD workflow darb'oħra jispezzjona l-rekwiżizzjoni u jiddetermina li l-ammont tax-xiri jaqbeż xi ammont dollaru maxium u rotot lill-maniġer diviżjoni għall-approvazzjoni.
8. Il-maniġer diviżjoni japprova l-rekwiżizzjoni xiri.

Noti

• Il-każ użu turi "nodfa" mmexxija bl-ebda rifjuti jew jumps.
• Kull approver għandu l-abbiltà li japprova jew jirrifjuta l-rekwiżizzjoni kif ukoll jipprovdi kummenti bil-miktub. Dawn huma illoggjat fil-audit trail.
• Jekk maniġer responsabbli tiċħad l-rekwiżizzjoni xiri fi kwalunkwe punt, l rekwiżizzjoni PO huwa "mejjet" u l-proċess għandu jinbeda mill-bidu.
• Workflow tinnotifika lill-oriġinatur f'kull pass tal-proċess.
• Ebda firem miktuba — il-klijent determinat (wara xi rakkomandazzjonijiet qawwija) li l-audit trail kif ipprovdut permezz istorja workflow, serva verifika tagħhom jeħtieġ.
• Isforz — hija ħadet madwar tliet ġimgħat bniedem biex jimplimentaw din is-soluzzjoni.

Konklużjoni

Din is-soluzzjoni tiggwida MOSS bħala żvilupp u run-time pjattaforma. Il-klijent kien kapaċi li jwieżen karatteristiċi ewlenin Moss awtomat proċess tan-negozju rutina dik affettwata kważi kull impjegat fil-kumpanija. Bl-eċċezzjoni ta 'servizz web sempliċi (li fih innifsu tiggwida MOSS), kważi l-ebda attwali "ipprogrammar" kien meħtieġ.

Is-soluzzjoni sservi wkoll bħala "vetrina" għall-klijent, turi karatteristiċi kif differenti ħażiż jistgħu jiġu kkombinati biex tinħoloq applikazzjoni ta 'negozju kompletament dehru u jiġġeneraw opportunitajiet ġodda ta' konsulenza fil-futur.

Glossarju

MRO: Manutenzjoni, tiswija u l-operazzjonijiet. Dan ix-xiri tipikament jinkludu oġġetti bħal notepads, siġġijiet, kompjuters personali, printers, mowbajls u simili.

This may be obvious to many, but while studying for my MOSS programming exam, I learned that it’s pretty easy to get the actual XML from a search query via the user interface.

One quick method is as follows:

• Access advanced search.
• Perform a search that returns some data.
• Edit the page (via site settings).
• Change the XSL to the following:

<?xml Verżjoni="1.0" encoding="UTF-8"?>
<XSL:stylesheet Verżjoni="1.0" xmlns:XSL="http://www.w3.org/1999/XSL/Transform">
<XSL:output metodu="xml" Verżjoni="1.0" encoding="UTF-8" inċiż="iva"/>
<XSL:template jaqblu="/">
<pre>
<XSL:copy-of tagħżel="*"/>
</pre>
</XSL:template>
</XSL:stylesheet>

• Hit apply.
• View Source in the browser.

Note that the <pre> 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 times I created some customized search results.

This ought to work for dataviews as well, though I have not tested that out as yet.

I see that Eric Kraus was faced with a requirement normally met with a content query web part. Il-problema? He was in a pure WSS environment with no access to the CQWP. Rather than curling up in the fetal position (an urge I have to fight every day, it seems), he came up with solution that at least gives WSS shops a fighting chance to succeed. It’s described hawn.

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

I first picked up this link from joris poelmans blog at http://jopx.blogspot.com/.

Even if you’re like me, in that you have not had to do much hands-on work for content management, this is well worth 20 minutes of your time to read.

Using the API, one can:

• Export and import content very easily.
• Re-parent content. If you want to export some content from a site "A" and send it to site "B" but in a totally new place in the hierarchy, this is possible.
• Export content from a site A and import selected bits into site A.
• Re-link content (jiġifieri jittrattaw ma 'l-hyperlinks).

Someone on the Internets was asking about how to create a calculated column on a list that would show a value formatted as "[User] – [Status] – [Post]" as in "Paul Galvin – Xorb [ħielsa] Beer – The Beach".

Paul would go in and update his entry in the list and the calculated column would update appropriately. The [User] għandu default għall-utent jidħol / taġġorna l-lista tal-.

A calculated column cannot use "volatile" funzjonijiet bħall- [Me] jew [Illum]. I solved it in a test environment with these steps:

1. Create a text column named "Current User".
2. Issettja valur default tagħha li [Me]
3. Create a calculated column called "Calc Test".
4. Issettja l-valur tagħha = [User attwali]

I marru fil-, Żied punt mal-lista u maħduma.

Stajt ġiet effettwati minn dan għal 9 xhur u nara li n-nies fuq il-MSDN u forums Usenet għandhom dan too.l

Kultant, meta tagħmel aċċess għad-dokument kelma (jew tipi oħra doc) minn librerija dokument tikkawża Internet Explorer li sempliċiment tiġrifa u jmorru lil hinn (tieħu l-tabs magħha jekk xi huma miftuħa).

Dan MS hotfix tista issolviha: http://support.microsoft.com/kb/938888

Wkoll, hemm xi deskrizzjoni dwar il-problema hawn:

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

Ħarsa ġenerali:

Maħluq lista drawwa li tamministra tip kontenut ma 'xi kolonni tużżana.

Miżjud hija għal paġna u mbagħad permezz SPD, konvertita ħsieb data.

Problema:

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>
            Current Status:
            <XSL:value-of select="@Current_x0020_Status"></XSL:il-valur tal->
          </td>
        </tr>
      </XSL>
    </tabella>

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".

While thrashing madly about, looking for a solution, I instead referred to "@Recruiter" and behold! — that actually returned back the current status. I expected it to return back the recruiter when I did that.

Soluzzjoni:

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".

Take Away:

SPD provides authoritative Xpath expressions for rows & columns in a data view.

Tieni, it shows the actual data. So for example, a column of type shows this:

<nobr><medda><A HREF="/sites/Corporate/HumanResources/TalentAcquisition/_layouts/userdisp.aspx?ID=17">Galvin, Paul</A><img border="0" height="1" width="3" src="/_layouts/images/blank.gif"/><a href=’javascript:’ onclick=’IMNImageOnClick();return false;’ class=’ms-imnlink’><img name=’imnmark’ title=” transkonfinali =’0′ height=’12’ width=’12’ src=’/_layouts/images/blank.gif’ alt=’No presence information’ sip=’PGalvin@xxx.com’ id=’imn_77,type=smtp’/></a></medda></nobr>