Category Archives: April 2008

Vivos et Simplex: Facies et forma InfoPath tantum legere, (InfoPath species Services musco)

5 Restituo

Illic 'a vulgaris negotium hujusmodi missionem:

  • User implet quasi forma InfoPath.
  • Forma suscipitur.
  • Diu procul fluxum workflow processus amet.
  • Dum currit workflow, Mutari nolimus quemquam formam dolor.

Hoc exemplum office.microsoft.com describes how to create a separate "view" and mark the whole view as read-only. This is a workable approach but has the drawback that you’ve effectively created two entire versions of the same form and must now keep them in sync manually. If you add a field to the editable view, you must then add it to the non-editable view as well. Super tempus, cum diversis tincidunt, there can be some divergence.

Vel hoc posset operari in quibusdam meliora:

  • Add a new field to the form called "IsEditable".
  • Verum pone eius defaltam ad valentiam.
  • Promoveant cum publicantes MUSCUS.
  • In workflow, statuet pretium IsEditble falsae.
  • Revertere ad formam.
  • Add a rule that "upon open of the form", disable vestri falsum est, nisi ipsum cum IsEditable.

The drawback to this approach is that all the fields will still be editable on the screen. The user can get a false impression that they can actually change content. You can mitigate that by putting in some text that the form is disabled, Page per litteras summum magnum rubrum possibile,.

Una project, I created a "workflow status" considerabit. As the workflow progressed, it would update specific status fields that had been promoted from the form. When the user opened the form, the "open form" regere automatically switched ut usura visum et habuit a nice status paulo summary.

</finem>

Scribet ad mea blog.

Uti Semaphores in SharePoint Designer workflow ne Infinita ansas

6 Restituo

It’s possible to cause an endless loop in a SharePoint Designer workflow. A common implementation pattern like this causes the problem:

  • Partum a workflow, et se associant album.
  • Indicant quod incipere debet in Partum a novus items et items existendi update.
  • A step in the workflow updates a field in "Current Item".
  • Cum current item mutata, incipiat de novo workflow.

Prohibet infinitas ansa, peragendam simplex semaphore:

  • Adde situs agmen (aut agmine album / library genera contentus, si non es usura).
  • Abscondas a edit page (factu, si locus agmen via proprietatum, ut facile, si non agmine album).
  • In workflow, reprehendo, si valor semaphore agmen blank.
  • Si est blank, et posuit illud non valet Dilígite procedere.
  • Si est, non est blank, Statim exitus.

Hoc potest fieri solutio satis nuanced, pendentium, et huiusmodi negotium requisita, sed cum Ive 'been opus illud exemplar a operabilium.

</finem>

Technorati Tags:

Scribet ad mea blog.

Tincidunt: Quomodo sciam SharePoint?

3 Restituo

UPDATE: 04/25/08: Aenean aliquam erat iactata super postes et invenit link to this article: http://www.networkworld.com/news/2008/032608-microsoft-sharepoint.html?page=1. I make note of it because in addition to asking, "how do I learn sharepoint?", some people ask "why should I learn sharepoint?". That article partly answers the later.

In novissimo aliquot menses, dozen plus folks trans planete fuerint petens et emailing me generali quaestione, "How do I learn SharePoint?"

Vix ego auctoritate, sed ego eo successu (melius et studio in omni tempore) so I thought I’d document my personal road map. Others may find it valuable.

Priusquam id faceret,, EGO iustus volo ut mihi manifestum est quod facere, ex his etiam plurium personarum emails et MSDN / Columnaeque academiæ ejusdem naturae SharePoint, that there is huge developer interest in getting up to speed with WSS/MOSS. I wonder what it’s going to be like a year from now … bonum ingenium facile invenire SharePoint? The same? Are folks committing themselves to the platform at a rate sufficient to keep up with demand for good resources? How could you even figure something like that out short of a WAG?

Pauli roadmap

I was full time employed by the good folk at Conchango while I followed this road map. This means that from a learning perspective, I was actively engaged in projects as I followed the steps I outline below.

Nonnullus basic condiciones

Nam hoc mundo intrantes, duo sunt key acronyms:

  • WSS: SharePoint Fenestra Muneris
  • MUSCUS: Microsoft Muneris SharePoint Server

WSS is "free" in sarcina ut suus fenestras server 2003 (aut saltem potest downloaded a MS). I put quotes around free because you need a box, Valida o /, et fortasse licenciam SQL (though there’s a "free" genus tam SQL).

MOSS is built on top of WSS and extends it. There is no MOSS without WSS. MOSS is not free.

Ne forte die una, Donec aliquam mox habes diam commercium, it’s important to learn the differences. Verbigratia, potens textus partem, Quaero Web content Parte, is a MOSS feature and not available WSS. People often make the incorrect assumption that CQWP is available in WSS and then end up scrambling for a stop-gap measure when they realize their error.

Ledo Books

I started working with WSS/MOSS on about 01/02/2007. I had a little prior experience with SPS 2003 but very little. To get myself started, Ego emit duobus libris recensentur hie (http://paulgalvin.spaces.live.com/lists/cns!1CC1EDB3DAA9B8AA!203/).

I started with the big blue administration book. Naturally, it covers administration. Simul, circumspectis igitur omnibus providet MUSCUS features (et uultus tam WSS).

Enim me, Details non est tanta, quot meminisse (donee tempus adquirendi nunciavimus scriptor) but it’s good to know the boundaries. (Sequor idem aditus in 1st persona jaculatores ludere in PC vel Xbox — I enter a room and tend to make a counter-clockwise loop until I get back where I started. I just feel better knowing the shape of the box I’m in.)

Lectis libro magnum hyacintho, I would read the entire Inside WSS book. It dives deeply into issues that developers care most about.

Partum a Rectum Opera

Ut faceret vel bene uti ambitu progressionem, vos opus a fenestra server plena titulique operating ratio SharePoint Designer, Visual Bulla 2005 (2008 operatur, Sed quaedam instrumenta tamen utile fuerit portaverat ut scripturam hanc articulum), InfoPath 2007 and some other stuff. There are many good blog entries describing this process. I’d have a look at these two:

Praeter, Andreas Connell experientiarum participes eius hic cum VMWare:

Use your favorite search engine to see what other people do. It’s a useful learning exercise in and of itself.

Spend a few minutes angrily denouncing the fact that you need a server environment on which to do development. Sed … don’t bother blogging about it or posting it to MSDN forums. It’s already been done 🙂. Pro, embrace it and move on. You’ll be better off for it.

Adepto nunciavimus

Credo quod MS SharePoint certificationem semita, quae consistit quattuor volutpat, is exhaustive. I suggest that you follow their online preparation guide and do your best to understand each of the areas of the test.

Ego noli suggest that you take the exam just to pass it. Ego noli suggest that you use one of the "brain dump" style 3rd party "tools" for passing MS tests. If you can take the test, transibo eam, fundatur in compositum tua dirigebar studio et manus-in experientia,, firmior eris elit et job candidatus eam.

There are four tests in two "tracks":

Elit:

Admin:

I recommend that developers study for all of these exams. You’ll be strong for them, tamen credo, si est exsultástis Fusce volutpat, vos adepto a.

Inveni WSS version esse aliquanto magis deposcendis quam debita MUSCUS versions, much to my surprise. I was in a class recently and several others made the same point.

Dum enim studebat 70-542 exem (MUSCUS progressum) I tracked my study resources. These may be helpful to you as well: http://paulgalvin.spaces.live.com/Blog/cns!1CC1EDB3DAA9B8AA!192.entry

Plug te in Community

In SharePoint communitas est Vividiorque, fortis et crescit maior omne tempus.

Vis at consequat ante:

  • Blogs
  • Forums
  • Codeplex
  • Aliquam

Blogs

Si non intelligere RSS, stop everything and learn it. It will take 10 minutes addiscere, fortasse alio 10 minutes inveniet lector RSS Lorem fundatur (Ego similis Google Lector scriptor, www.google.com / lector).

Start by adding this blog to your RSS reader 🙂

Postero, addunt www.sharepointblogs.com to your reader. They aggregate many blogs into a single feed.

Super tempus, you’ll find blogs that are not aggregated that way. Just add them individually.

I subscribe to a few dozen blogs which I’ve accumulate over the last year. If you want, Possum exportare mea album quod email.

Tandem, you may want to start your own blog. I personally think that a series of blog entries describing a "newbie’s" profectus cognita WSS / MUSCUS esset an interesting seriei. Utinam ipse facit.

Forums

Ego foro coetus actuose participent duo: MSDN et SharePoint University.

Forums are excellent places to learn. People ask questions ranging from the very simple ("How do I create a site column") ad panicked ("My server is down!") hypothetica magis consilium rogationibus.

Lorem ipsum dolor saporem, venture out and start replying. Short of directly interacting with a customer, nam nihil melius esse quam manus dolor.

Codeplex

Ad www.codeplex.com.

Reprehendo eam et quaerere inceptis SharePoint.

Subscribant quotidie Summary Codeplex tua pascuntur in lectori pascite.

Addere novum inceptis ad tuum SharePoint pascuntur lector.

Tandem, post lectionem autem forums et deorsum versus tua WSS / MUSCUS daemonum, considera quod compositio tua project codeplex.

Aliquam

Ut scribo is blog ingressu, multus of populus have coepi usura SharePoint Aliquam.

It’s hard to characterize Twitter. You’ll just have to check it out yourself.

Conclusio

That wraps up my roadmap and makes me current. I just started using Twitter two weeks ago.

WSS/MOSS is a very cool platform and the community is growing all the time. Use community resources to improve your skills and enjoy the journey!

</finem>

Scribet ad mea blog.

Donec eros velit: Videtur sicut magnus SharePoint Tergum / Solutio Restituo

Aliquam responsum

In New Jersey SharePoint User Group occurrentes nocte, Microsoft Sr. Product artifex DuWayne Harrison obtulisset Microsoft Data Protection Procurator 2007. DuWayne was great (data in auxilium, et nomina audit ex una et altera urna non recolo). Vos can adepto praesentationis materias hie.

Usque nocte, Ego numquam de DPM.

Im 'non a persona ratio typus admin, so I’m writing this from SharePoint consultant’s perspective and may get some of the words wrong. Mihi, DPM is a backup/restore solution for Microsoft "stuff":

  • Files
  • SQL
  • O / S
  • Rectum apparatus (vivo tergum de VM, etsi ipsa VM cursor Unix).
  • Peperit metalli recuperare (i.e. EXITIALIS hardware elit).

Ultra quod effercio, which I would consider to be minimal requirements for any kind of "real" tergum / restituo Product, DPM also has built-in intelligence for SharePoint. It understands about server farms and lets you restore:

  • Totam databases (e.g. content, config, etc).
  • Collectiones Site
  • Singula loca
  • Singulis (e.g. documenta).

The actual restore process involves extracting the target data from the backup and save it into a "restore farm" atque inde, movens ad producendum environment (sive ubicumque uolueris restituet). I think this is seamless, but there was a lot of emphasis on the need for a "restore farm". The restore farm does not need to match the production environment in every particular (maxime in physicis topology) sed indiget ut compositus secundum Templates, versions, etc.

Consummationem non vidi finem amet, but DuWayne did show screen shots and some live demos. It seems to be as good as it needs to be, Nulla at mediocri.

I was particularly struck by the pricing. Obviously, ne me ad hanc, Aliquam sed orci magna est dure, ut opinor, (in USD):

  • $600 pro se DPM.
  • Hardware pro servo DPM (et media et omnia vasa socius).
  • $450 Singulis server vos volo ut tergum sursum ("enterprise" licenciam).

A quinque server villam esset constant ad summum:

  • $600 nam DPM
  • $450 x 5 servientes = $2,250

Totalis sumptus in dissentiet: $2,850

In praxi, it would be less. You wouldn’t necessarily need to have DPM installed on each web front end, enim. You don’t necessarily need enterprise licenses either.

The user interface is seems very simple probably would not require any special training to get up to speed. I did ask about that specifically and there is apparently a 1.5 die genere praesto, si opus sit, non apparet alicui, quod accipere.

Omnia in omnibus, Puto suus dignum certe quaerimus, si vestri 'vultus pro notitia sicco illic præsidium solutionem SharePoint.

</finem>

Scribet ad mea blog.

Technorati Tags:

Aliquam: http://twitter.com/pagalvin

Ambulare per-: Lorem ipsum Lorem ipsum Lorem figere sedes Unregister Bug

2 Restituo

Quam multa sciunt, Aliquam molestie pharetra dummodo per Microsoft hie secundum hos gradus est cimex quod potest reproducere:

  • Mauris class cum Max moli 10 alumni.
  • Register –> Total available seats properly decrements by one. Result: 9 praesto cathedras.
  • Unregister: –> Bug. Total available seats should increment by one. It does not. Result: 9 praesto sedibus per SharePoint, sed in eo,, Sunt 10 praesto cathedras.

Solutio: Uti SharePoint Designer corrigere workflow.

Primum, open up the site. The folder list for me looks like this:

imaginem

If we have a look at the "Attendee registration" workflow, we see that there is a step labeled "Enforce seating policy". It looks like this:

imaginem

This step in the workflow updates the item by incrementing the "Filled Seats" metadata column on the course. If we pull that up in more detail, videmus:

imaginem

Quod suus omnes notitia postulo fige unregistration workflow.

Si workflow flip super ut unregistration, there is no similar workflow step. Add it as follows:

1: Expand "Attendee unregistration" et aperire XOML (vide prius si screen iecit errabis).

2: Addunt novam variabilem workflow, "New Filled Seats" of type "Number".

3: Assign a value to "New Filled Seats" ut ostensum:

imaginem

4: Pleni sedes ad decrementum 1:

imaginem

5: Cursus eget augue, relatus:

imaginem

6: Make sure all the steps are in the right sequence. Enim me, is vultus amo is:

imaginem

7: Consummetur workflow iterum aedificare illud.

8: Test.

</finem>

Scribet ad mea blog.

Technorati Tags: ,

Random Sabbati mane Observatione

2 Restituo

Praeter has duas hebdomadas fui et unum generum mihi, quod multum quidem videri, dolor populus operantes in SharePoint (ut Consultores aut baculum) quis non aliquando in ephemeride, twitter, Videtur conscius publicum nuntium vel tabulis forum sicut MSDN SharePoint University, Cornelius LinkedIn tenere vel profiles, etc. They are pure information consumers. Not bad, iustus interesting.

</finem>

Technorati Tags:

Scribet ad mea blog.

Quaero Web content Parte: Loquens ad Novum Eboracum SharePoint Users Group

Aliquam responsum

Te loquente cum collega, Natalya Voskresenskaya, apud Lugduni SharePoint Users Group occurrentes Wednesday May 7th.

Gratias Bob Fox ad iaciendum in nostris nomina proni et coadiuvans nos adepto occasionem!

Locus est pars vitae nostrae contentus Textus Quaero speramus aliquid utilis notitia ut duo distincta Audientiis:

  • Negotium users (tincidunt non-): Quemadmodum quaedam communia negotia problemata solvenda configured CQWP potest sine coding.
  • Tincidunt: Show how CQWP can be extended to do some pretty interesting things that a business user wouldn’t normally feel comfortable doing themselves. This part of the presentation will help business users understand what’s possible using this web part so that they can provide better and more realistic requirements to their developer partners.

Hic est titulus NYSPUG CATAPHRACTUS maturius hoc septimana:

"Using Content Query Web Part to Solve Business Problems".

MOSS 2007’s Content Query Web Part (CQWP) users possit creare consuetudinem sententiae a multis notitia queried, et nunc ipsum quod in uno. Quamquam hereditas eius potens query & contentus bene polito, CQWP saepius underrated et despiciens pluma. CQWP is both a "data extraction engine" (reperio usquam documentis vel album items in a collection site) et quoque in primo genere evidenter præsentationem tool quod users ad moderari contentus est quomodo sistuntur per HTML involvens et splendor format styles ut paene quolibet modo.

In hoc demo-grave sessionem, CQWP solvere dabunt operam uti eu Vestibulum facilisis mollis neque per ostentationem.

  • uti default vultus CWQP, possidet Nisl id Aenean Curabitur tellus

  • use CWQP as a reporting tool anywhere in a site collection via filter criteria such as "all documents created today".

  • respice immutare & sentio of negotium notitia query consequitur ad exaggerandam, notitia ostendere columnis adiectis, notitia ostendere eget format, aliique.

  • CQWP quomodo potest auxilium typus contentus administrationis (i.e. invenietis omnia documenta particularis potentia ictum mutato content type ut intelligant a definitione CT).

  • exsequor nonnullus of limitations CQWP

  • opibus providere index enim proficiebat artes CQWP, possidet blogs, ECQWP Codeplex project & Documenta MSDN.

</finem>

Scribet ad mea blog.

Technorati Tags:

GRAVITER SharePoint Integration: Fáciant simplex Query

2 Restituo

This is a continuation in my FAST coding mini-series for SharePoint folk. The bit of code below executes a search for the term "test" in FAST via a Console application. Obviously, suus saliunt, omit, et salire ad obvolvendum hanc partem sive logica intus telam application page:

usura System;
usura System.Collections.Generic;
usura System.Linq;
usura System.Text;
usura System.Collections.Specialized;
usura Com.FastSearch.Esp.Search;
usura Com.FastSearch.Esp.Search.Http;
usura Com.FastSearch.Esp.Search.Navigation;
usura Com.FastSearch.Esp.Search.Query;
usura Com.FastSearch.Esp.Search.Result;
usura Com.FastSearch.Esp.Search.View;
usura System.Collections;

Spatium nominale Conchango
{
    genus InvokeSimpleFASTQuery
    {
        static Irrita Main(filum[] args)
        {

            #regionem Initialize communicatio nostra cum ieiunium
            ISearchFactory searchFactory;

            NameValueCollection nameValueCollection = novum NameValueCollection();

            nameValueCollection.Add("fastsearchengine", "Com.FastSearch.Esp.Search.Http.HttpSearchFactory");
            nameValueCollection.Add("Com.FastSearch.Esp.Search.Http.QRServers", "fastdemoback:15100");
            nameValueCollection.Add("Com.FastSearch.Esp.Search.Http.RequestMethod", "GET");

            searchFactory = SearchFactory.NewInstance(nameValueCollection);

            #endregion

             Immittendi query

            filum queryString = "test";

            Quaero query = novum Quaero(queryString);

            query.SetParameter(BaseParameter.RACEMIFER, falsum);
            query.SetParameter(BaseParameter.NAVIGATIO, verum);
            query.SetParameter(BaseParameter.NAVIGATION_DEEPHITS, 100);

            ISearchView searchView;
            searchView = searchFactory.GetSearchView("sharepointconn");

            IQueryResult Ex = searchView.Search(query);

            Consolandum.WriteLine("Total results from search: [" + result.DocCount + "].");

            int docCounter = 0;

            Dum (docCounter < result.DocCount)
            {

                docCounter    ;

                IDocumentSummary thisDocSummary = result.GetDocument(docCounter);

                Consolandum.WriteLine("[" + docCounter + "]: " + thisDocSummary.GetSummaryField("url").StringValue);

            } // Dum

            Consolandum.ReadLine();
            #endregion

        }
    }
}

Procreat ex sequentibus:

imaginem

</finem>

Scribet ad mea blog.

Technorati Tags: ,