Flokkaskjalasafn: SharePoint

Notkun “Einstakling eða hóp” í reiknað dálki

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

Neðsta lína, þetta virkar ekki í WSS 3.0 (eða Moss).

Þegar að bæta við reiknað dálk, 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, it tells you:

One or more column references are not allowed, because the columns are defined as a data type that is not supported in formulas.

Lausn: 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.

Useful links on calculated fields in general:

Quick disclaimer: I believe the above to be true and accurate, but I’ve seen enough clever tricks here and there in MOSS/WSS that I wouldn’t be extremely surprised (agog if you will) 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, please let me know!

MOSS / WSS segir mér: “Síðan hefur verið breytt af öðrum höfundi á …” en í raun, það var ekki.

We did some heavy duty re-organizing of our site taxonomy via "Manage Content and Structure". For reasons unknown to me, þetta ferli (þó að vinna í helstu) broke some navigation links in the quick launch. The broken links are characterized by:

  • Wrong URL. Til dæmis, it should be "/sites/departments/HumanResources/…". Hins, the new link is "/sites/Corporate/HumanResources/…".
  • Endurtekin bitar á fyrirspurninni band af fyrirsögninni, eins og í:

/staður / deildir / HumanResources / _layouts / viewlsts.aspx?BaseType=0?BaseType=0?BaseType=0?BaseType=0

That’s easy enough to fix via site settings/navigation. Except, MOSS kynnir mig með þetta þegar ég reyna að gera það:

mynd

Staðreyndin er, enginn er að gera allar breytingar þar (innskot frá mér, auðvitað).

A fljótur leita snýr upp þessa MSDN umræður: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1691577&SiteID=1

William Heurdier setur það út fallega í penultimate (og með 10/02/07) staða:

Staðreyndin er:

Til að núllstilla skemmd fyrirsagnir, þú þarft að :

– fjarlægja allar skrár undir skemmd lið

– fjarlægja skemmd stefnir

– Af listanum stillingum, add a removed list to the quick launch (Þetta endurfæða a non skemmd stefnir)

Þú ert þá gott að fara….


Sharepoint Expert – Cap Gemini Sogeti Sviss

Ég var dálítið ruglaður af því að ég hélt að vilja fara á flakk síðuna, make the change and then get hit with the "page was modified" message. Lokum, 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!

</enda>

Gerast áskrifandi að bloggið mitt!

Vandamál með “Hlé Þangað Dagsetning” virkni í SPD-skapa workflows

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

Bakgrunnur:

Við hafa a viðskipti kröfu þar umhverfis verkfræði framkvæmdastjóri þarf að tryggja að 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 (eða aðstoðarmaður hennar) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

Umhverfi:

Moss, 64 hluti, raunverulegur vél umhverfi (þróun kassi), 2 netþjónum (SQL á vefþjóninum #1, allt annað á þjóninum #2).

Vandamál:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. Hins, það virkar ekki vel út af the kassi (fyrir okkur).

  1. The workflow starf var ekki áætlað að keyra, ever. I discovered this by reading through Christopher er hvítur (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:\>

    Það var óvart vegna en auðveldlega leyst:

    C:\>stsadm -o setproperty -propertyname "job-worfklow" -propertyvalue "every 1 mínútur á milli 0 og 59" -url HTTP://localhost

    Aðgerð lokið.

    C:\>

    Þegar aðgerð sem, the first "In Progress" workflow rekinn fljótt upp og gerði það starf.

  2. Því miður, the next one didn’t work as expected. Sem betur fer, Christopher refers us hér (http://support.microsoft.com/kb/932816). As of writing of this entry, við erum að bíða eftir að IT deild til að fá að snarhasti, but it does look promising. Our copies of the affected .dll’s do not share the same byte size, svo vonandi mun þetta leysa vandamál.

Lausn:

Re-running the stsadm -o setproperty command seemed to prod the workflow timer awake. It would, u.þ.b. 7 mínútum síðar, actually wake up and continue along with the workflow.

Spurningar / Mála sem:

Hlé þar til dagsetning virkar ekki.

Hlé þar til dagsetning ekki aftur.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"

MRO Workflow dæmisögu með mosa, SPD, InfoPath & vefur þjónusta.

Yfirlit

Þessi færsla lýsir dæmisögu sem lýsir í raun MRO (Viðhald, Viðgerðir og rekstur) workflow samþykki aðferð til framkvæmda í mosa.

Þetta er ekki overtly tæknilega umræðu, heldur þjónar að veita raunverulegur-veröld dæmi sem sýnir hvernig MOSS vettvang hitti alvöru-heiminum verða.

(This entry is cross posted between http://paulgalvin.spaces.live.com og http://blogs.conchango.com)

Bakgrunnur

The client’s MRO process had been characterized by the following

  • Manual approval process.
  • Some support using excel spreadsheets.
  • Irregular approval process. The same MRO purchase approval process would vary day to day, person by person.
  • Lots of paper and hand-written signatures — purchase requisitions required up to 3 written signatures before final approval.

The objectives of this project included:

  • Fully automate the process.
  • Enforce enterprise standards for approval.
  • Provide consolidated view of MRO purchasing to various managers.
  • Detailed audit trail.

As a side effect of the solution, written signatures were no longer required.

Approval Process

The approval process consists of four "swim lanes": Originator, Direct manager, Functional manager and division manager.

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. Sumir sinnum, the originator does not have the technical expertise to fill out the PO requisition. Til dæmis, a user may want to requisition a new laptop computer, but does not know the best vendor, IT standards, o.fl.. Í þessu tilviki, the originator works with IT and IT actually fills out the requisition.

Direct manager:

This is the direct manager of the originator (which may be different from the person who actually entered the PO requisition into MOSS). Direct managers must approve the PO requisition before the system seeks approval further down the line.

Functional Manager:

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. Til dæmis, IT purchases are approved by an IT functional manager.

Division Manager:

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

The Solution

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, master data, audit trails and other features.

InfoPath forms services: A MOSS component, this enables users to fill out purchase requisitions via a web browser.

SharePoint Designer (SPD): We used SPD to implement the automated workflow process.

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. Sjá hér for a technical deep dive on this subject and our reasons for using it.

Custom Lists: MOSS user profiles provided a given user’s direct manager, but did not provide most of the data that controlled workflow decisions (e.g. whether the divisional manager is required to approve the PO requisition). 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) functionality with auditing and security out of the box.

Use Case

This use case illustrates how the solution fits together:

  1. Paul wants a new laptop. He describes his needs to Vivek, an IT person familiar with corporate laptop standards, preferred vendors, o.fl..
  2. Vivek logs into 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 (e.g. "IT" or "Finance").
  3. SPD based workflow starts, determines Paul’s direct manager and routes the requisition to his manager, Stacy.
  4. Stacy approves the purchase requisition.
  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 approves the requisition.
  7. SPD workflow again inspects the requisition and determines that the purchase amount exceeds a maxium dollar amount and routes it to the division manager for approval.
  8. The division manager approves the purchase requisition.

Skýringar

  • 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.
  • If a responsible manager rejects the purchase requisition at any point, the PO requisition is "dead" and the process must be started from the beginning.
  • Workflow notifies the originator at every step of the process.
  • No written signatures — the client determined (after some forceful recommendations) that the audit trail as provided via workflow history, served their auditing needs.
  • Effort — it took approximately three man weeks to implement this solution.

Ályktun

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 (which itself leverages MOSS), almost no actual "programming" was required.

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

Glossary

MRO: Viðhald, repair and operations. These purchases typically include items such as notepads, chairs, personal computers, printers, cell phones and the like.

MOSS / WSS Leitarniðurstöður (og dataviews): skoða hrátt XML gögn

Þetta kann að vera augljóst að margir, en á meðan að læra fyrir mosa forritun prófinu, Ég lærði að það er frekar auðvelt að fá raunverulegt XML úr leit í gegnum notendaviðmót.

Einn fljótur aðferð er eins og hér segir:

  • Aðgangur ítarlegri leit.
  • Framkvæma leit sem skilar einhverjum gögnum.
  • Breyttu síðunni (í gegnum stillingar á síðuna).
  • Breyta XSL til eftirfarandi:

<?XML útgáfa="1.0" Kóðun="UTF-8"?>
<
XSL:stílsíðu útgáfa="1.0" xmlns:XSL="HTTP://www.w3.org/1999/XSL/Transform">
<
XSL:framleiðsla aðferð="XML" útgáfa="1.0" Kóðun="UTF-8" undirlið=""/>
<
XSL:sniðmát passa="/">
<
fyrirfram>
<
XSL:afrita af velja="*"/>
</
fyrirfram>
</
XSL:sniðmát>
</
XSL:stílsíðu>

  • Högg sækja.
  • Skoða Source í vafranum.

Athugaðu að <fyrirfram> 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 sinnum ég búið til nokkrar sérsniðnar leitarniðurstöður.

Þetta ætti að vinna fyrir dataviews eins vel, þótt ég hafi ekki prófað það út eins og enn.

Engin CQWP fyrir WSS? Prófaðu þetta…

Ég sé að Eric Kraus was faced with a requirement normally met with a content query web part. The problem? He was in a pure WSS environment with no access to the CQWP. Rather than curling up in the fetal position (hvöt ég að berjast á hverjum degi, það virðist), he came up with solution that at least gives WSS shops a fighting chance to succeed. It’s described hér.

Ljómandi og ítarlegt yfirlit yfir innihald stjórnun API

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

Ég tók fyrst upp þennan tengil frá Joris Poelmans blogginu á http://jopx.blogspot.com/.

Jafnvel ef þú ert eins og mig, í gerðir þú ekki hafa þurft að gera mikið snertið ekki-á vinnu fyrir innihald stjórnun, þetta er vel þess virði 20 minutes of your time to read.

Notkun API, maður getur:

  • Auðveldlega inn og flytja efni mjög.
  • Re-parent content. If you want to export some content from a site "A" and send it to site "B" en í algerlega nýjum stað í stigveldi, þetta er possibleness.
  • Útflutningur efni frá a staður A og flytja valin bita inn á síðuna A.
  • Re-hlekkur efni (þýðir takast með öllum tengla).

WSS, doc libs & listar, Reiknaðir dálka þátttöku [Mig]

Someone on the Internets was asking about how to create a calculated column on a list that would show a value formatted as "[Notandi] – [Staða] – [Staðsetning]" as in "Paul Galvin – Drykkja [frjáls] Bjór – The Beach".

Paul would go in and update his entry in the list and the calculated column would update appropriately. The [Notandi] ætti sjálfgefið að notandi fer inn / uppfæra listann.

A calculated column cannot use "volatile" virka eins og [Mig] eða [Í dag]. I solved it in a test environment with these steps:

  1. Create a text column named "Current User".
  2. Setja sjálfgefið gildi hennar að [Mig]
  3. Create a calculated column called "Calc Test".
  4. Setja gildi = [Núverandi Notandi]

Ég fór í, við hlut á listann og það í uppnámi.

Hléum hrun IE þegar aðgangur skjöl í WSS / MOSS skjal bókasafn

Ég hef verið plága við þetta fyrir 9 mánuði og ég sjá að fólk á MSDN og Usenet ráðstefnur hafa það too.l

Stundum, þegar aðgangur orð skjal (eða öðrum doc gerðir) úr skjali bókasafni veldur Internet Explorer til að einfaldlega hrun og fara burt (taka allar flipa með það ef einhverjar eru opin).

Þetta MS snarhasti má leysa það: http://support.microsoft.com/kb/938888

Einnig, það er einhver lýsing um vandamál hér:

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

Mun alvöru XPath skref áfram?

Yfirlit:

Búið til sérsniðna lista sem stýrir gerð efnis með nokkrum tugi dálka.

Bætt það á síðu og þá í gegnum SPD, breytt í upplýsinga skoðað.

Vandamál:

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:gildi-af>
          </td>
        </tr>
      </XSL>
    </borð>

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.

Lausn:

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.

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

<nobr><span><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=” border=’0′ height=’12’ width=’12’ src=’/_layouts/images/blank.gif’ alt=’No presence information’ sip=’PGalvin@xxx.com’ id=’imn_77,type=smtp’/></a></span></nobr>