SharePoint Shop Talk Recap for Thursday 10/01/09

Aliquam responsum

I’ve noticed that people seem to be waiting until the last minute to register for SharePoint Shop Talk sessions. Last Thursday, at about 11:45AM, we had nine people register, which is a very small number. Autem, at one point, we had 18 aut 20 people signed in, so at least nine people signed up for it 45 minutes or less before the call. I’m not complaining, just observing.

We had a full schedule of questions and discussion topics and couldn’t get to all of them. As usual, we’ll pick up where we left off this coming Thursday.

Here’s the recap:

  • Vamshi asked about building a WSS environment that has SP1 and not SP2. You can download that configuration here:

    http://www.microsoft.com/downloads/details.aspx?FamilyId=4191A531-A2E9-45E4-B71E-5B0B17108BD2&displaylang=en. And someone else suggested looking here: http://technet.microsoft.com/en-us/windowsserver/sharepoint/bb400747.aspx.

  • We had a (grata) surprise return visitor. A few weeks previous, Blue had asked us a question that left everyone on the call a little sad because we couldn’t help. His problem and solution are really fairly complicated, but it boils down to creating a data view web part with a range of filtered dates (not just one single filtered date, which is easier). He may write up a blog entry on this and if does, I’ll link to it. In the course of the discussion, he referred everyone to these two links:
  • Looping in SharePoint designer – can it be done? The answer is “yes” in some narrow cirumstances. Autem, to do it, you need to do some tricky stuff that is hard to conceptualize, hard to implement, suus 'ferreus ... iustus patet difficile ad CIMICO,,en,In panel de consensus - nec hoc potest nisi auxilio,,,en,Si vos postulo looping,,en,actiones vel partum mos stillabunt in in Studio visual,,en,prob non facile cadunt in nos,,en,sed quid est hoc,,en,Loquens de tristi,,en,Marcus vincit in "Fac quod Quam Tristis Panel" ab award,,en,frustra,,en,postulantes de drag quod occumbo visum notitia ex textus partem,,en,In sem est valde interesting, et, si quis habet callidus solution,,en,Hic est forsit,,en,habet enim aliquid necesse est quod DVWP percolatur, ut in bibliotheca documentum refert retro dozens vel documentis,,en,Hoc operatur magnam,,en,users opus eius, ut incenderent illos qui documentis et ad CD,,en,Hoc genus agibili per visum in fenestra rimor,,en. The panel’s consensus – don’t do this if you can help it. If you need looping, create custom actions or drop down into visual studio. Utique, si tibi usura SPD, you prob can’t easily drop down into VS, but it is what is is, miserabile.
  • Speaking of sad, Nancy wins the “Make the Panel Sad” award by (futilely) asking about drag and drop from a data view web part. The scenario is very interesting and if anyone has a clever solution, placet me cognoscere. Here’s the problem: she has a DVWP that is doing some necessary filtering on a document library that returns back dozens or more documents. This works great. Autem, her users need to take those documents and burn them to CD. This is doable using a windows explorer type view, Quomodo autem hoc ex DVWP? We couldn’t think of a good answer. Can you?
  • Laura Rogers, secuti per de Lori Gowan www.endusersharepoint.com Fama (et alibi,) made us aware of the fact that attachments to InfoPath forms can be submitted via a web service to an image library in SharePoint. Ex arca archa! That is a very interesting fact with some very interesting implications.

That’s pretty much it. I probably missed something, but hopefully you get the gist of it.

Even though I know you won’t actually sign up until noon, Thursday, here’s the registration link for the next session, Thursday 10/08 ex 12:30 ad 1:30 PM EDT: https://www.livemeeting.com/lrs/8000043750/Registration.aspx?pageName=0z40kg9nb0t0842f

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin

SharePoint Shop Talk Thursday 10/01 @ 12:30 PM EDT (tomorrow!)

1 Respondere

SharePoint Shop Talk registration is up and ready for tomorrow.

We have a few questions teed up that address some management issues (dev/test/prod and syncing up service packs), email notifications (how to select people to email based on metadata of a document) and some discussion around using InfoPath forms services in an FBA environment.

Ut semper,, if you want to talk about a topic:

You can read about past SharePoint Shop Talks on my blog here: http://paulgalvin.spaces.live.com/?_c11_BlogPart_BlogPart=blogview&_c=BlogPart&partqs=cat%3dPublic%2520Speaking

Register for the session here: https://www.livemeeting.com/lrs/8000043750/Registration.aspx?pageName=h6hm9ptg8zt7302t

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin

Windows Live spatia et Twitter Counter

1 Respondere

I was DM’d a message from twitter today and thought I’d blog the answer.

The question is: “Hey Paul, quick one for you,how did you get the twitter counter into your live space as the script code is blocked when saved Thx”

I did this by adding a custom html widget to my live spaces page and using the little code snippet:

<a href="http://twittercounter.com/?username=pagalvin" 
 title="TwitterCounter for @pagalvin"> 
 <img msgstr="http://twittercounter.com/counter/?username=pagalvin" 
 latitudo=88 
 height=26 
 style="border:none" 
 alt="TwitterCounter for @pagalvin">
</a>

This uses a version of the twitter counter widget interface that gets past the windows live censor thing that we all hate so much and wish would get a bad case of poison ivy.

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin

Technorati Tags:

Approbatio vero moderandis coetus InfoPath in FBA Opera

1 Respondere

Habeo sumptu approbatione processus necessaria ad peragendam usura InfoPath in formis fundentur authenticas (FBA) environment utendi formis servicia (dicentur telam InfoPath).

Ibi sunt duo coetus processus operatur huiusmodi approbatione:

  • User implet sumptui fama subiicit approbatione.
  • Quod ad primum gradum probatorem coetus saltem an email.
  • Primo gradu et approbat, vel consideret abnegat fama probatorem.
  • Si primo gradu illud acceptatur, secundo ratio notifies probatorem.

Ex parte rerum InfoPath, Habeo diversas partes abscondam / apparent utrum user fundatur in est unum membrum coetus eorum approbatione.

In environment FBA nomen usoris() functio semper redit blank, miserabile. What I’ve done is set up a a custom list called “Approval Groups”.

Columnas quoque addas non album.

Cum forma recludit, habet hoc sicut a regula:

image

Per "agrum profectus est scriptor valor" Adest:

image

Dicens: Hoc est basically: Quaero mos coetus, approbante album et spurcamen quod vultus pro query, a versu ubi Title scriptor valor = "Consilium".

Si redit, ut valor aliquis, then the current user is a member of that group. I know it contains that value because the string length is greater than zero.

Close the loop by securing the individual items in the Approval Group list. At run-time, si user non current accessum habent ad congruam cautionem item ut tum query non resalutaturum, string-length will be zero and now you know the current user is not part of that group. You can use that fact as needed in the form.

This is a super brief write-up. I’m pressed for time or I’d provide more detail.

I don’t know how relevant it is that I’m in an FBA environment. This would probably work well in a non-FBA environment but I can imagine cases where this would be useful.

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin

Technorati Tags: ,

Shop SharePoint metent Disputatio (09/24/09 edition)

Aliquam responsum

8 aperi nobis consummata SharePoint Shop Q Disputatio&A session yesterday. During that session, cooperuit nos sequentibus locis:

  • Quam Emíttet Email a workflow creavit usura a altus formatted SharePoint Designer.
  • Aenean ubi hoc inter SharePoint 2010 et maxime SharePoint Fenestra Muneris 3.0 (libera versione SharePoint).
  • We discussed jQuery maintenance and management. More specifically, "Ubi oportet ire jQuery?” We had a great discussion around this topic and one interesting new ideas (mihi) is the idea of a content delivery network. This bing search pulls up a lot of interesting data on the subject: http://www.bing.com/search?q=microsoft+content+delivery+network&FORM=DLSDF7&pc=MDDS&src=IE-SearchBox
  • Quis mentionem quod partes (aut forsitan in omnibus) of the up-coming mega conference in Las Vegas in October will be broadcast over the internets. Check out this site for more information: http://www.week3.org/Events/default.aspx
  • We talked about RSS. That discussion covered a lot of ground. There’s a CodePlex project that does better RSS than what you get out of the box and www.endusersharepoint.com Rogers habet aliquod bonum articulis ab Laura in sessionibus uti DVWP ædificare bona RSS.

That about covers it. People seem to be getting a lot of help from these so we’ll keep them going.

In Palatium efficientiam, I’ve already set up next week’s SharePoint Shop Talk session. You can register here: https://www.livemeeting.com/lrs/8000043750/Registration.aspx?pageName=h6hm9ptg8zt7302t

Si vis ad participant, ignis off an email ad questions@sharepointshoptalk.com, ledo me Twitter (@ Pagalvin) vel licentia a ineo hic.

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin

SharePoint Shop Talk Thursday 09/24 @ 12:30 PM EDT

Aliquam responsum

Paratus adnotatione est, et cras SharePoint Shop at Disputatio 12:30 PM.

Dum haec in conloquio poscit, tabula experti SharePoint scriptor cape pro quaestionibus via email, via live meeting or directly over the phone. We do our best to provide independent expert advice on all topics related to SharePoint.

Email vestris quaestionibus ad "Questions@sharepointshoptalk.com", Twitter eas mihi, licentia a ineo hic iustus ostendo sursum in vocationem et quaerere.

Et quaerite prudentiam de membris audientibus etiam suscipiat.

Possis legere quidam recaps superioribus SharePoint Shop Disputatio sessionibus in mea blog.

Hoc septimana iam scimus puteus alloquitur quaestionibus pertinentibus ad workflow (constans ventus) et investigent nominare paucos.

Register hie: https://www.livemeeting.com/lrs/8000043750/Registration.aspx?pageName=dv3m7cl30sxkq2n1

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin

Hoc Tuesday SharePoint Shop Disputatio 09/17/09 12:30 Ut PM EDT 1:30 PM EDT

Aliquam responsum

Disputatio fit hoc Jovis proximo SharePoint Shop, 09/17 ad 12:30PM EDT.

Quid est SharePoint Shop Disputatio? It’s a one hour conference call where a panel of SharePoint pro’s answer questions. Send your questions to "Questions@sharepointshoptalk.com", leave a comment on my blog here or just ask them out loud on the call. The panel tries to offer several different approaches to solving the underlying problem behind the question and just generally provide unbiased expert advice.

Hoc septimana permanemus eodem panel, possidet ipse, meis duos Arcovis Socii Harry Jones et Natalya Voskresenskaya et Laura Rogers de SharePoint911.

Breviter recapping ultima septimana - sumus plus quam quaestiones respondere possimus,, ita hoc septimana, we’ll start off with those. We had 34 registrants puto 25 people actually joined the call. We covered a wide variety of subjects that I would say were 75% User finem ordinantur, possidet:

  • Consilia in contentus de glomeratque sub-sites sites ut summo gradu interiore conquisita et trans site.
  • Ictum customizing editform.aspx usura SharePoint Designer.
  • De nobilis "colligere notitia de user" SharePoint Designer actio workflow.
  • Usura jQuery solvere quaestiones quaedam communia user interface.
  • Zona temporis quæstiones (pro locorum environment distributi)

Nos pluribus alias quoque texit, sed details me fugit,.

I promised to do follow up with a live meeting to dig into one of the questions and still need to do that.

Subcriptio hoc septimana scriptor hic sessionem: https://www323.livemeeting.com/lrs/8000043750/Registration.aspx?pageName=bhj8dbrswhv1hv8r

Hoc septimana, we’re going to talk about at least:

  • Strategies for managing and getting at version history for documents
  • Suitability and ideas around using SharePoint as a front end that allows your customers to view some financial data.
  • Workflow questions (more).

We’ll see and hear you there!

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin

SharePoint Diei Novi Eboraci

Aliquam responsum

Ive uploaded meus praesentationis ad Novum Eboracum SharePoint Diei hie: http://cid-1cc1edb3daa9b8aa.skydrive.live.com/self.aspx/SharePoint/Follow the Yellow Brick Road to SharePoint Mastery.pptx

Sed non valde utiles, si non ad praesentia, sed spes addit multum inter Nota nunc et Tampa, when I present it again. That would give it more legs and context and be more generally useful.

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin

Si id non Vestibulum ...

1 Respondere

Irem per ingentem acervum MSDN divulgationis impetro tergum meus uxor mea 30 seconds ut locus daretur et noua MSDN divulgationis Ego venit trans antenatum articulo de Loquela MS Page portitor workflow fundamentum et duxi, non esse frigus ad integrari cum omnibus SharePoint? It would be kind of neat to be able to say “Create site named [frigus site] in collection site [ubera ursum]” into my cell phone and have it do that. I can imagine an architecture where speech server hands off the commands to a workflow application that does all the work. That’s very easy logic to implement on the server side of the fence.

In UI, you’d have to do something to get it rolling. I’d probably go to a “speech monitor” kind of SharePoint site that has some jQuery running that monitors a queue that is updated by the workflow application and shows, in realis tempore, what’s happening.

That would be a pretty crazy technology train right there. Cell phone dialing up to speech server on some machine. Workflows bridging the gap between Speech Server and SharePoint. jQuery enhancing a plain Jane SharePoint UI.

Estne aliquid practica hoc component? Who knows. Who cares?

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin

Dentes tui sicut potest esse paulo consulens Educens

Aliquam responsum

[Note: This article cross-posted to Finem User SharePoint hic: http://www.endusersharepoint.com/2009/09/09/sharepoint-a-case-study-in-ask-the-expert/]

Aliquando, when you’re working as a consultant (as a profession, or in a consultative role within your company), you find yourself living in an Onion story. The Onion has a series of articles called “Ask an [expert] de [some problem]". This follows the famous “Dear Abby” format where a concerned person is asking for personal advice. The onion’s “expert”, autem, is so focused on his/her area of expertise and current problems that the expert ignores the question entirely and rambles on about his area of expertise. As consultants, we need to keep that in mind all the time and avoid falling into that trap. It’s classically described like this – “when you use a hammer all day long to solve your problems, everything starts to look like a nail.” We professional consultants are always on guard against that kind of thing, but we come into contact with people who are serious professionals in their own role, but are not consultants. They don’t have the same need or training to do otherwise.

Ultima septimana, I wrote about one of my company’s clients and an on-going project we have to enable high quality collaboration between various eye doctors in the US and Canada performing clinical research on rare disease. In addition to leveraging core SharePoint features to enable that collaboration, we’re also working an expense submission and approval process. It’s complicated because we have so many actors:

  • A handful of individuals at different doctors’ practices who can enter expenses on line.
    • There are over 40 doctors’ practices.
    • At some practices, the doctor uses the system directly.
    • At many practices, the doctor’s staff uses the system directly.
  • A financial administrator (who works for my direct client) who reviews the expenses for accuracy and relevancy, approving or denying them at the organizational level.
  • A 3rd party accounts payable group. These people pay all of the bills for out client, not just bills coming out of the rare disease study.

The Accounts Payable group has been a challenge. Working with them yesterday reminded me of the Onion series. In my role as business consultant, I explained the need to the accounts payable company:

  • Clinical studies sites (doctors’ practices) incur study-related expenses.
  • They log onto the “web site” and enter their expenses using an online form. In hoc, the “web site” is hosted with SharePoint and the expenses are entered into an InfoPath form. Expense receipts are scanned, uploaded and attached directly to the form.
  • An automated workflow process seeks approval from the appropriate financial administrator.
  • You, dear 3rd party AP company – please review and approve or deny this expense. I’ll send it to you any way that you want (within reason).At this point in the discussion, I don’t really care how it needs to be bundled. I want to work with the AP group to understand what they need and want.

When I explained the need, the 3rd party took a deep dive into their internal mumbo jumbo lingo about expense approval processes, Oracle codes, vice presidential signatures, 90 day turn-arounds, etc. And panic. I shouldn’t forget about the panic. One of the bed rock requirements of the consulting profession is to learn how to communicate with people like that who are themselves not trained or necessarily feel a need to do the same. Among other things, it’s one of the best parts of being a consultant. You get to enter a world populated with business people with completely different perspectives. I imagine it’s a little bit like entering the mind of a serial killer, except that you aren’t ruined for life after the experience (quamquam in mentem procuratoris AP ambulatio in hortis non est 🙂 [see important note below***] ).

One of the great things about our technical world as SharePoint people is that we have ready-made answers to many of the very valid concerns that people such as my AP contact have. Is it secure? How do I know that the expense was properly vetted? Can I, as the final payer, see all the details of the expense? How do I do that? What if I look at those details and don’t approve of them? Can I reject them? What happens if the organization changes and the original approver is no longer around? Can we easily change the process to reflect changes in the system? Can I revisit this expense a year later if and when I get audited and need to defend the payment?

As SharePoint people, we can see how to answer those questions. In my client’s case, we answer them more or less like this:

  • InfoPath form to allow sites to record their expenses and submit them for approval.
  • Sites can return to the site to view the status of their expense report at any time.
  • As significant events occur (e.g. the expense is approved and submitted for payment), the system proactively notifies them by email.
  • The system notifies the financial administrator once a report has been submitted for approval.
  • Financial administrator approves or denies the request.
  • Upon approval, the expense is bundled up into an email and sent to the 3rd party payer organization.
  • The 3rd party payer has all the information they need to review the expense and can access the SharePoint environment to dig into the details (primarily audit history to verify the “truth” of the expenses).
  • 3rd party payer can approve or reject the payment using their own internal process. They record that outcome back in the SharePoint site (which triggers an email notification to appropriate people).
  • In future, it would be nice to cut out this stilly email process and instead feed the expense information directly into their system.

In conclusion, there’s a life style here that I describe from the professional consultant’s point of view, but which applies almost equally to full time employees in a BA and/or power user role. Work patiently with the experts in your company and extract the core business requirements as best you can. With a deep understanding of SharePoint features and functions to draw upon, more often than not, you’ll be able to answer concerns and offer ways to improve everyone’s work day leveraging core SharePoint features.

***Maximus note: I really don’t mean to compare AP people to serial killers. Autem, I could probably name some AP pro’s who have probably wished they could get a restraining order against me stalking them and asking over and over again. “Where’s my check?” “Where’s my check?” “Where’s my check?"

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin