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

Bottom line, dit nie werk nie in WSS 3.0 (of MOSS).

Wanneer jy 'n berekende kolom, 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, dit vir jou vertel:

Een of meer kolom verwysings word nie toegelaat, omdat die kolomme word gedefinieer as 'n data tipe wat nie ondersteun word in formules.

Work Around: 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.

Nuttige skakels op berekende velde in die algemeen:

• Die gebruik van [Me] in 'n berekende kolom
• Voorbeelde van formule uitdrukkings (vergunning van http://jopx.blogspot.com/2007/10/calculated-fields-in-windows-sharepoint.html)

Vinnige disclaimer: Ek glo die bogenoemde om waar te wees en akkurate, maar ek het genoeg gesien slim truuks hier en daar in MOSS / WSS dat ek nie sou baie verbaas (nuuskierig as jy wil) 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, laat weet my asseblief!

We did some heavy duty re-organizing of our site taxonomy via "Manage Content and Structure". For reasons unknown to me, hierdie proses (al die werk in die belangrikste) broke some navigation links in the quick launch. The broken links are characterized by:

• Wrong URL. Byvoorbeeld, it should be "/sites/departments/HumanResources/…". Egter, the new link is "/sites/Corporate/HumanResources/…".
• Herhaal stukkies op die navraag string van die opskrif, soos in:

/terreine / departemente / human / _layouts / viewlsts.aspx?BaseType=0?BaseType=0?BaseType=0?BaseType=0

That’s easy enough to fix via site settings/navigation. Except, MOSS bied my met hierdie wanneer ek probeer en doen dit:

Die feit is, niemand is om enige verandering is daar (Afgesien van my, natuurlik).

'N vinnige soektog draai hierdie MSDN forums bespreking: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1691577&SiteID=1

William Heurdier lê dit uit mooi in die die voorlaaste (soos van 10/02/07) pos:

Feit is:

Korrupte opskrifte te herstel, jy het om te :

– verwyder al die lyste onder beskadig opskrif

– verwyder beskadig opskrif

– Uit die lys instellings, add a removed list to the quick launch (Dit herstel 'n nie beskadig opskrif)

Jy is dan goed om te gaan….

---

Sharepoint Expert – Cap Gemini Sogeti Switserland

Ek was 'n bietjie verward omdat ek wil om te gaan na die navigasie bladsy, make the change and then get hit with the "page was modified" message. Uiteindelik, 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!

</einde>

Skryf in op my blog!

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

Agtergrond:

Ons het 'n besigheid vereiste waar 'n omgewing ingenieurswese bestuurder nodig het om te verseker dat 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 (of haar assistent.) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

Omgewing:

MOSS, 64 bietjie, virtuele masjien omgewing (ontwikkeling boks), 2 servers (SQL op bediener #1, alles op bediener #2).

Probleme:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. Egter, dit werk nie goed uit die boks (vir ons).

1. Die workflow taak is nie om te hardloop, ever. I discovered this by reading through Christopher White se (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:\>

   Dit was 'n verrassende uitslag, maar maklik opgelos:

   C:\>stsadm -o setproperty -propertyname "job-worfklow" -propertyvalue "every 1 minute tussen 0 en 59" -url http://localhost

   Operasie suksesvol voltooi.

   C:\>

   By dit te doen, the first "In Progress" workflow vinnig afgedank word en het dit se werk.

2. Ongelukkig, the next one didn’t work as expected. Gelukkig, Christopher refers us hier (http://support.microsoft.com/kb/932816). As of writing of this entry, ons wag vir die IT-afdeling te verkry dat die hotfix, but it does look promising. Our copies of the affected .dll’s do not share the same byte size, so hopelik sal dit die probleem op te los.

Work Around:

Re-running the stsadm -o setproperty command seemed to prod the workflow timer awake. It would, ongeveer 7 minute later, actually wake up and continue along with the workflow.

Vrae / Kwessies:

Stop Tot Datum werk nie.

Stop Tot Datum hervat nie.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"

Oorsig

Hierdie inskrywing beskryf 'n gevallestudie van 'n werklike MRO (Onderhoud, Herstel en Bedryf) die workflow goedkeuring proses geïmplementeer in Moss.

Dit is nie 'n openlik tegniese bespreking, maar dien in plaas daarvan om 'n werklike wêreld voorbeeld wat toon hoe die Moss-platform met 'n werklike wêreld behoefte om voorsiening te maak.

(Hierdie inskrywing gepos is 'n kruising tussen http://paulgalvin.spaces.live.com en http://blogs.conchango.com)

Agtergrond

Die kliënt se MRO-proses is gekenmerk deur die volgende

• Handleiding goedkeuring proses.
• Sommige ondersteuning met behulp van Excel-sigblaaie.
• Irregular approval process. The same MRO purchase approval process would vary day to day, persoon aan 'n persoon.
• Baie van die papier en handgeskrewe handtekeninge — inkoop tot op 3 geskrewe handtekeninge voordat finale goedkeuring.

Die doelwitte van hierdie projek:

• Outomatiseer die proses volledig.
• Dwing onderneming standaarde vir goedkeuring.
• Verskaf gekonsolideerde siening van MRO die aankoop van verskeie bestuurders.
• Detailed audit trail.

As a side effect of the solution, geskryf handtekeninge is nie meer nodig.

Goedkeuring-proses

Die goedkeuring-proses bestaan ​​uit vier "swem lane": Originator, Direkte bestuurder, Funksionele bestuurder en afdeling bestuurder.

Originator:

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. Sommige tye, the originator does not have the technical expertise to fill out the PO requisition. Byvoorbeeld, kan 'n gebruiker wil rekwisisie 'n nuwe skootrekenaar, maar nie weet wat die beste verkoper, IT standaarde, ens.. In hierdie geval, the originator works with IT and IT actually fills out the requisition.

Direkte bestuurder:

Dit is die direkte bestuurder van die skepper (wat anders kan wees van die persoon wat eintlik die PO rekwisisie het in MOSS). Direct managers must approve the PO requisition before the system seeks approval further down the line.

Funksionele bestuurder:

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. Byvoorbeeld, IT purchases are approved by an IT functional manager.

Divisie Bestuurder:

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

Die Oplossing

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

MOSS: Serves as the platform off which everything else "hangs". MOSS provides bedrock services for security, meester data, oudit paaie en ander funksies.

Path vorm dienste: 'N mos-komponent, Dit stel gebruikers in te vul inkoop via 'n webblaaier.

SharePoint Designer (SPD): Ons gebruik SPD die workflow proses te implementeer.

Web Service: 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. Sien hier vir 'n tegniese diep duik oor hierdie onderwerp en ons redes vir die gebruik van.

Custom Lyste: MOSS user profiles provided a given user’s direct manager, but did not provide most of the data that controlled workflow decisions (bijv. of die Divisie Bestuurder wat nodig is om die PO rekwisisie goed te keur). We used custom lists in an "Enterprise Data" tuiste van data soos "Divisie Bestuurder goedkeuring Dollar Bedrag" in stand te hou., "Funksionele gebied Bestuurder" and so forth. Lists integrated very nicely with InfoPath and also provide create/update/delete (CRUD) funksionaliteit met ouditering en sekuriteit uit die boks.

Gebruik Saak

Hierdie gebruik geval illustreer hoe die oplossing saam pas:

1. Paul wants a new laptop. He describes his needs to Vivek, 'n IT-persoon wat vertroud is met korporatiewe laptop standaarde, voorkeur-verskaffers, ens..
2. Vivek log in MOSS, 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 (bijv. "IT" or "Finance").
3. SPD gebaseerde workflow begin, bepaal Paul se direkte bestuurder en roetes die rekwisisie aan sy bestuurder, Stacy.
4. Stacy keur die aankoop rekwisisie.
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 keur die rekwisisie.
7. SPD workflow inspekteer weer die rekwisisie en bepaal dat die aankoop bedrag 'n maksimum weer dollar bedrag en roetes dit vir goedkeuring aan die Divisie Bestuurder.
8. Die Divisie Bestuurder keur die aankoop rekwisisie.

Notas

• Die gebruik geval toon 'n "skoon" 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.
• As 'n verantwoordelike bestuurder verwerp die aankoop rekwisisie by enige punt, die PO rekwisisie is "dood" and the process must be started from the beginning.
• Die Workflow kennis van die skepper by elke stap van die proses.
• Geen geskrewe handtekeninge — die kliënt bepaal (Na 'n paar kragtige aanbevelings) dat die ouditspoor via workflow geskiedenis verskaf, hul ouditering gedien moet.
• Poging — it took approximately three man weeks to implement this solution.

Slot

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 (wat self maak gebruik van MOSS), bykans geen werklike "programmering" nodig was om.

Die oplossing dien ook as 'n "showcase" vir die kliënt, demonstrating how different MOSS features can be combined to create a fully featured business application and generate new consulting opportunities in the future.

Woordelys

MRO: Onderhoud, repair and operations. These purchases typically include items such as notepads, stoele, persoonlike rekenaars, drukkers, selfone en dies meer.

Dit kan duidelik baie, maar terwyl jy studeer vir my MOSS ontwikkeling eksamen, Ek het geleer dat dit is redelik maklik om die werklike XML te kry van 'n soektog via die gebruikerskoppelvlak.

Een vinnige metode is as volg:

• Toegang gevorderde soek.
• 'N soektog wat gee 'n paar data.
• Wysig die bladsy (via werf-instellings).
• Verander die XSL na die volgende:

<?xml weergawe="1.0" encoding="UTF-8"?>
<xsl:style weergawe="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:uitset metode="xml" weergawe="1.0" encoding="UTF-8" streepje="ja"/>
<xsl:sjabloon ooreenstem met="/">
<pre>
<xsl:kopie-of kies="*"/>
</pre>
</xsl:sjabloon>
</xsl:style>

• Getref toe te pas.
• Sien Bron in die leser.

Let daarop dat die <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 kere wat ek geskep is om persoonlike resultate.

Dit behoort te werk vir dataviews sowel, maar ek het nie getoets is wat uit nog.

Ek sien dat Eric Kraus was faced with a requirement normally met with a content query web part. Die probleem? He was in a pure WSS environment with no access to the CQWP. Rather than curling up in the fetal position ('n drang Ek moet elke dag te veg, dit lyk), he came up with solution that at least gives WSS shops a fighting chance to succeed. It’s described hier.

Stefan Goßner has put together a terrific 4-part series on the SharePoint Content and Deployment API hier. 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/.

Selfs as jy soos ek, 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 (meaning deal with all the hyperlinks).

Someone on the Internets was asking about how to create a calculated column on a list that would show a value formatted as "[Gebruiker] – [Status] – [Plek]" soos in "Paul Galvin – Drink [vry] Beer – Die strand ".

Paul would go in and update his entry in the list and the calculated column would update appropriately. Die [Gebruiker] moet standaard aan die gebruiker aangaan / opdatering van die lys.

'N berekende kolom kan gebruik nie "vlugtige" funksies soos [Me] of [Vandag]. I solved it in a test environment with these steps:

1. Skep 'n teks kolom genaamd "Huidige Gebruiker".
2. Stel die verstek waarde na [Me]
3. Skep 'n berekende kolom genaamd "Calc Test".
4. Stel die waarde = [Huidige Gebruiker]

Ek het in, 'n item op die lys en dit het gewerk.

Ek het al geteister deur dit vir 9 maande en ek sien dat mense op die MSDN en Usenet forums het dit too.l

Soms, wanneer hulle toegang tot 'n woord dokument (of ander doc tipes) uit 'n dokument biblioteek veroorsaak Internet Explorer om net te crash en gaan weg (neem al die oortjies met dit as 'n oop).

Dit MS hotfix kan dit op te los: http://support.microsoft.com/kb/938888

Ook, daar is 'n paar beskrywing van die probleem hier:

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

Oorsig:

Maak 'n persoonlike lys wat die bestuur van 'n inhoud soort met 'n paar dosyn kolomme.

Het bygevoeg dat dit na 'n bladsy en dan via SPD, omskep in 'n data view.

Probleem:

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>
            Huidige Status:
            <xsl:value-of select="@Current_x0020_Status"></xsl:waarde van>
          </td>
        </tr>
      </xsl>
    </tafel>

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

Terwyl dors soos 'n besetene oor, op soek na 'n oplossing, I instead referred to "@Recruiter" en kyk! — that actually returned back the current status. I expected it to return back the recruiter when I did that.

Oplossing:

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

Wegneem:

SPD bied gesaghebbende Xpath uitdrukkings vir rye & kolomme in 'n data-oog.

Tweede, it shows the actual data. So for example, 'n kolom van die tipe toon hierdie:

<nobr><span><A HREF="/sites/Corporate/HumanResources/TalentAcquisition/_layouts/userdisp.aspx?ID=17">Galvin, Paul</'N><img border ="0" height="1" width="3" src="/_layouts/images/blank.gif"/><a href = "javascript:’ onclick = 'IMNImageOnClick();terugkeer valse;’ class = "MS-imnlink '><img name=’imnmark’ title =” border =’0′ hoogte = '12’ breedte = '12’ src = "/ _layouts / images / blank.gif’ alt = "Nee teenwoordigheid inligting’ sluk = 'PGalvin@xxx.com’ id = 'imn_77, type = smtp' /></1></span></nobr>