Category Archives: January 2008

Aliquam arcu

I thought some people might be interested in my blog’s statistics. You can use mine as a benchmark to compare your own.

I’m running my blog on windows live spaces. They collect stats for me and I don’t know any way to control that. It’s good as far as it goes, but it’s fairly limited in that I can’t do much actual analysis with it. I’d love, enim, to be able to generate a listing of my most frequently hit posts but I can’t do that without a prohibitive manual process. If someone knows better, indica mihi,.

Ago spatia status indicare mihi: hits in die totalis, total hits for the week and total hits since day zero. It also tells me what people did to get to my blog (e.g. Google, MSDN forum nectunt, etc).

In aliqua vias, a "hit" Patet. Si hoc legere scis sententia nunc, youve fere certe commemorantur, una uolnerati.

RSS is a little confusing. On one hand, I see individual RSS hits all day long. Sed, I also see RSS "sweeps". A sweep is when I see 20 aut 30 RSS hits all within a one or two second window. I assume these are automated things like google checking in on my site, maybe alienis navigatores … not sure. They are definitely some kind of automated process. I cannot tell, autem, how many of my total hits are automated and how many have an actual human on the other side. I would guess at least 100 hits per die sunt automated.

Ad numeros!

Scripsi mea blog primum ingressum in July 27th, 2007.

Scripsi proxime 60 Cum igitur Blog, quam 50 quae directe pertinent ad SharePoint.

Aliquam in me servo semita of coepi in a cotidie basis ad finem Septembris spreadsheet.

Menstrua incipiat:

Prima septimana: Summa Animi
Octobris 1,234
November 2,162
December 3,071
January 2008 4,253

A totalis Mensis

Mense Summa Animi
Octobris 6,620
November 11,110
December 13,138

Princeps aqua marcas

Typus Summa Animi
Optima dies 958
Optimum Hebdomadae 4,253
Die Summa Animi Quia adipiscing 42,438

Sum interested in alios’ stats. If you care to share yours in the comments, placet fac!

</finem>

Technorati Tags:

Dominica matutina Funny: “Yeah, Yeah, Yeah. Mauris, mauris, mauris.”

De sex annos, filii quattuor annorum susum sunt custodiae et Inventionem alveo "Turpis impetus" specialis (potest hoc). He was very young at the point and I was always worried what he might see on a show like this and how he might take it. I didn’t want him to develop, enim, quis specialis metus de aqua vel LOQUITOR aliquid inconueniens ad amicos et forte faciat eius infantem amicus network ad fregerunt.

Discovery handles these kinds of subjects very well. It’s not about creating a timore aliquid, but rather to show how unusual it is for sharks to attack humans.

Ita, we’re watching it and there is this one particularly scary attack involving a small girl. As Discovery is building the drama of the attack, mea filius (qui semper perquam TURBATUS usquam), is getting very excited. I make some noises about how unusual it is for sharks to attack people, and how bad the poor girl must feel. I’m trying to explain that people recover from these events and become stronger for it. Autem, I had misinterpreted his excitement. He was not worried about the girl at all. Pro, dum percussione manus, refert me, "De loca amare! It’s terrific. It’s wonderful. Its a DREAM COME TRUE!"

Ego hoc hilares, but also very disturbing. On the one hand, Libenter — etiam paulo superbus — quod potuit fortis empathic affectus, cross-species though they may be. As humans, opus evolvere nostri "empathic musculi" ita loqui aut tu finire quasi huic In alia manu 🙂, he was feeling cross-species empathy toward a species who was exhibiting behavior inimical to his own. I was really struggling with this when the narrator used the word "paradigm". My son picked up on that and asked me what that meant.

At non facile describi ad quatuor anni, but I gave it a try. When I think of the word "paradigm", Thomas Kuhn is never far from my thoughts. Lego Compages de Scientific revolutionibus retro ad Mollis et melius peius, verbum "paradigma" is pregnant with extra meaning for me. (Modi sicut verbum "contactus" audito a Movie Lorem vocem dico me ubi videre quod movie [Ego libro erat melius]; Ego semper dicere ad ipse, "Donec!" quotiens vel audire aliquis dicere "contactus").

Usquam, Ego conatur explicare ad eum a Kuhnian definitio, quod suus "historica motus cogitationis" and that it’s a "way of thinking with a number of built-in assumptions that are hard to escape for people living at that time." Utique, non loquaris ad quatuor anni, so I’m trying to successively define it to smaller pieces and feeling rather proud of myself as I do so. (Ego iustus cognovit quod aliquis extra collegium cura me legere Kuhn!).

I’m just warming to the task when he interrupts me. Waving his hand in meae directionem et numquam assumptis oculos off aliud inhumanum turpis impetum, justi dicit, "Yeah, Yeah, Yeah. Mauris, mauris, mauris. ".

Adeo ut 🙂

Ad quod punctum, Placuit ad fugit, oratoriam loqui, sedere retro, et frui vigilantes loca impetum homines cum filius.

</finem>

Technorati Tags:

Transibit View View Ex User ID In InfoPath Forma

Nos a succrevit an InfoPath forma cum multiplex views sustinere novum mercedem / on-boarding process. When the company hires a new person, IS department et aliis coetibus opus ad actio (posuit stipendia, enable accessum ad conveniens applications, locant a desk, etc). We use on form but a different view of the form for each of those functions.

Ad hoc comitatu, maxime personarum in negotium processus sunt IT-sagaces, ita cum obvius forma, eorum Nubila est a "menu" view with buttons that direct them to their specific function. Autem, we needed to simplify things for the new hire’s direct manager. This person should not see any of the IT related stuff. In facto, videret unius formae secundum alias sententias videre nec optare.

In nobis, quod directe procurator scriptor propter directe ligatum ad formam humanitatem de a contactus electrix (quod sum semper volens vocant a "populus picker" enim causa).

Vestigia sunt:

1. In consilium modum, ad Exodus -> Forma Bene -> Aperire et salvum.

2. Lego "praecepta".

3. Novum regula cuius actio est "transibit ad considerandam" et cuius statu Aenean in Username() munus.

Username() redit "simplex" user name without the domain. If I log into SharePoint with credentials "domain\pagalvin", Username() redire "cervicalia".

The contact selector provides three bits of information for a contact. The "AccountID" portion is most useful for this scenario. The only thing that makes this even a little bit of challenge is that the contact selector (in mea environment usquam) redit in dominico et user ID, as in "domain\pagalvin". This prevents us from doing a straight-forward equality condition since AccountID ("Domain cervical") numquam aequare Username() ("Pillow").

Uti possumus in circuitu "continet" operante: AccountID continet Username().

Nos potest ulterius et pre-PROMOVEO durus coded dominico in fronte Username() elit ut nostri aequalitas reprehendo et eliminare periculo a falsa positivum in continet operante.

We would have REALLY like to automatically switch view for other users based on their AD security group membership. Verbigratia, cum membrum "IT Analytics" coetus aditus forma, automatically switch to the IT Analytics view. We didn’t have time to implement it, sed primum cogitatio est creare telam ministerium quod esset modus sicut "IsMemberOfActiveDirectorySecurityGroup", transire in Username() and return back true or false. Does anyone have any other, magis callidus idea? Is there any SharePoint function we can leverage from InfoPath to make that determination?

</finem>

Technorati Tags:

Accidens addens Codicis ad InfoPath Forma; Industria tollis

Cum in forma Bullae opus, we often add rules. You access the rules editor from the properties of the button.

Cum clicking circa cito, suus facile ad accidens click in "Edit Forma Codicis" pro "Regulae …".

Primum ego hoc, I canceled out of the code editor. Autem, conatus paulo post cum forma auditum, eam requiritur quod auditum ut "Administrator-probata forma Template (proficiebat)". I didn’t actually do any programming and I absolutely didn’t want to go through an unnecessary approval process. I was in a bit of panic at the time due to time constraints. To get past it, I simply restored a previous backup and continued. I had recently seen some blog posts about people going into the form’s XML to tweak things and I was afraid I would have to do something similar.

Hodie, I did it again. Hoc tempore, Paululum tempus solve is facile invenit manus mea.

Ad:

Instrumenta -> Forma Bene -> Vestibulum: "Aufer Codicis"

Non adepto multo facilius.

</finem>

Technorati Tags: ,

Minimum Obses requiritur InfoPath Formae

I needed to meet a security requirement for an InfoPath form today. In this business situation, a relatively small number of individuals are allowed to create a new InfoPath form and a much wider audience are allowed to edit it. (Hoc est novum conducere in-boarding forma per Humanum ipsum quod movet workflow).

Ad occursum rei, Ego creavit creata duo novum licentia campester ("Creare et update" et "update tantum"), fregit hereditatem forma bibliotheca et assignari permissions ad "creare, update" user et separata "update tantum" User. The mechanics all worked, but it turned out to be a little more involving than I expected. (Si tibi paulo tremulas in SharePoint permissions, reprehendo ex hoc blog post). The required security configuration for the permission level was not the obvious set of granular permissions. To create an update-only permission level for an InfoPath form, Fecit sequenti:

  1. Novum licentia gradu.
  2. Purgare omnes bene.
  3. Lego tantum sequenti a "List permissions":
    • Creare Items
    • Considerabit Items
    • Considerabit Application Pages

Eligendo haec bene permittit user ad update a forma, sed non creare.

The trick was to enable the "View Application Pages". There isn’t any verbage on the permission level that indicates that’s required for update-only InfoPath forms, sed vertit ex est.

Create-and-Update was even stranger. I followed the same steps, 1 per 3 above. I had to specifically add a "Site Permission" bene: "Use client integration features". Iterum, descriptio ibi non videtur sicut debet requiritur ad InfoPath forma, sed ibi est.

</finem>

Technorati Tags: ,

Quod “In-Inter” Sententia; Observationes in SharePoint Consulting

Miserabile, phase one of my last project has come to a close and the client has opted to move ahead by themselves on phase two. We did our job too well, as usual 🙂 I’m now between projects, specialis tempus virgam Consultores sicut ipse (as opposed to independents who must normally live in perpetual fear of in-between time 🙂 ). We staff consultants fill this time in various ways: Operantes cum Sales vulgares scribere rogationibus; implens in aliquis vel tergum a persona in hoc aut impar opus; studying; Blogging :). It’s hard to plan more than a few days in advance. At times like this, manus autem mea modico tempore, I like to reflect.

I’m almost always sad to leave a client’s campus for the last time. We consultants form a peculiar kind of relationship with our clients, unlike your typical co-worker relationship. There’s the money angle — everyone knows the consultant’s rate is double/triple or even more than the client staff. You’re a known temporary person. As a consultant, you’re a permanent outsider with a more or less known departure date. Tamen, comedetis prandium cum client, eos ad cenam et / vel bibit, buy crustulum in quadrigis, ire in capulus currit, dare / accipere feriae pecto — all the kinds of things that co-workers do. On one hand, you’re the adult in the room. You’re an expert in the technology which puts you in a superior position. SED CONTRA, you’re a baby. On day zero, Consultores non scire nomina, the places or the client’s lingo. Most times, Consultores numquam discere omnes.

Cum quae bene, you become very well integrated with the client’s project team. They treat you like a co-worker in one sense, and confidant in another. Since we don’t have a manager-style reporting relationship with the client, the project team often feels a little free to air their dirty laundry. They let their barriers down and can put the consultant into an awkward position, numquam sentientes sunt faciendo.

Consultants often don’t get to implement phase two and that never gets easy for me. I think this is especially hard with SharePoint. Phase one of of your typical SharePoint project covers setup/configuration, regiminis, Doct, basic contentus genera, etc. et in multis, amounts ad longam, extremely detailed discovery. That’s how I view my last project. We did all the basic stuff as well as execute some nice mini-POC’s by extending CQWP, foveant BDC nexus ad PeopleSoft, induxit satis complexu workflow cum SharePoint amet, touched on basic KPI’s and more. A proper phase two would extend all of that with extensive, fere ubique BDC, vere delicatus workflow, denique jubilantionibus et melius quaerere, monumentis centrum, excellere officia et probabiliter maxime, reaching out to other business units. Sed, suus 'non me, and that’s sad.

Fundatur in hoc recenti, I think it’s fair to say that a proper enterprise SharePoint implementation is a one year process. It could probably legitimately run two years before reaching a point of diminishing returns. Details matter, utique.

That’s the consultant’s life and all of these little complaints are even worse in a SharePoint engagement. Ut ego scriptum ante, SharePoint’s horizontal nature brings you into contact with a wide array of people and business units. When you’re working with so many people, te potest ita multis SharePoint potest auxilium comitatu magis efficiens, nisi tempore, facere melius… but you don’t always get to do them.

Saepius eu ex collegio primum respicere, before starting a consulting career 1995. We did get to do a phase two and even a phase three. Those were nice times. On the downside, autem, that means that that would mean a lot of routine stuff too. Managing site security. Tweaking content types. Creating views and changing views. Dealing with IE security settings. Restoring lost documents. Blech! 🙂

Postremo melancholia mood, Nescio ubi mallem esse (nisi ad calidum litore cum pulchra copia spiritus).

Non expectare ad adepto coepi implemented altera incepto SharePoint project.

(Circa nihil, Vestibulum ipsum scripsi in hac NJ Transit bus. I don’t think I made any friends, but one CAN blog on the bus 🙂 )

</finem>

Technorati Tags:

Dominica Funny: “Sunt es Non Bad”

Retro iuxta 1999, Sum consumptis multum hebdomadarum ex in Santa Barbara, CA, operantes enim a client, leaving my poor wife back here in New Jersey alone. I dearly love my wife. I love her just as much today as I did when she foolishly married me 1,000 years or so ago. Alicubi in linea, Ego signata a phrase, "Specialis timore", as in "Samantha has special fears." She as a special fear of "bugs", quod ad eam sunt non volat vel ladybugs, but rather microbes. She’s afraid of this or that virus or unusual bacteria afflicting our son, aut me, but never really herself. (Est etiam specialiter timere lamia, parvam malum pupas (maxime pagani) et subaquaneam accidentia; illa de-crevit speciali timore populus indutus in Santa Claus outfits).

Unum die, my co-worker and I decided to drive up into the nearby mountains near Ohai. At one point, we got out of the car to take in the scene. When we got back into the car, I noticed that a tick was on my shoulder. I flicked out the window and that was it.

Quod nocte, I told her about our drive and mentioned the tick. The conversation went something like this:

S: "Oooo! Those are bad. They carry diseases."

P: "Bene, Ego flicked eam fenestram."

S: "Sint mala licet. They can get under your skin and suck blood and transfer bugs. You better check your hair and make sure there aren’t any in your head!"

P: In vocem: "Deus meus! CAN THEY TAKE OVER YOUR MIND???"

S: Litteram Benigne me: "Nulla, sunt es non malum."

</finem>

Technorati Tags:

Vivos et Securus: Automatically Patefacio InfoPath Forma Ex SharePoint amet Email

UPDATE: Madjur Ahuja ostendit Donec a newsgroup disputatione: http://msdn2.microsoft.com/en-us/library/ms772417.aspx. It’s pretty definitive.

===

We often want to embed hyperlinks to InfoPath forms in emails sent from SharePoint Designer workflows. When users receive these emails, possunt click in pagina a email et ire directe ad InfoPath forma.

Hoc monstrum URL constructione operatur me:

http://server/sites/departments/Technical Services/InformationTechnology/HelpDesk/_layouts/FormServer.aspx?XmlLocation=/sites/departments/Technical Services/InformationTechnology/HelpDesk/REC REM RED Forms/REC2007-XII-18T11_33_48.XML&Source=http://server.corp.domain.com/sites/departments/Technical%20Services/InformationTechnology/HelpDesk/REC%20REM%20RED%20Forms/Forms/AllItems.aspx&DefaultItemOpen = I

Reponere bolded rubrum text cum nomen in forma, ut ostenditur in sequens screenshot:

imaginem

Note quod est multum difficile-coded viam in quod URL, as well as a URL-encoded component. If this is too hard to translate to your specific situation, try turning on alerts for the form library. Post a form and when you get the email, Lorem ipsum fontem ponere oportet omne quod youll 'animadverto.

Astute readers may notice that the above email body also shows a link that directly accesses the task via a filtered view. I plan to explain that in greater detail in a future post.

</finem>

Technorati Tags: