Vivos et Securus: Uti commodo ut A Text Field scriptor Value in SharePoint Forma

5 Restituo

Coepi ludens circa cum mauris yesterday. I’ve been wanting to do this for a long time, semper Paulus Grenier coepi scriptum eius series de commodo enim End Users in venerabilis www.endusersharepoint.com web site. As I use it, I hope to add a series of “Quick and Easy” posts like this one. This post describes how to set a known text field’s value to anything you want.

In hoc missione, Ego creavit consuetudinem album cuius "novum" forma spectat ut ostensum:

image

Hoc est nova forma consuetudo album cum default Title agmen et duo album columnas (non site columnas; Si nihil aliud arbitror).

Vile est finis arbitrarium agri attribuunt, "DefaultMeFieldNoSpaces" (te potest dico sum frenum de ignavus cum "non spatia" res ingressus in, at ego eum in novissimo dictum condimentum).

Hoc frenum de commodo operati me:

<script typus ="text/javascript">

  $(munus() {

    $('Input[title = DefaultMeFieldNoSpaces]').attr(
        {valor: Tu sunt in a twisty error locis, omnibus. '});

  });

</script>

Ut ego hoc frenum de commodo est dicens, “find me any input tag whose title = DefaultMeFieldNoSpaces. Igitur, posuit omnes eorum valores ad nobilem phrase ex vetus computer ludum. "

Cum tantum esse unum agrum in forma cum a title aequalis "DefaultMeFieldNoSpaces" nos sunt certus assignandi a valorem ad agrum et non aliis.

Quod de agro cuius nomen habet spatia in eam? It’s nearly the same:

<script typus ="text/javascript">

  $(munus() {
     $('Input[title = assignant Field Cum Tractus]').attr(
        {valor: Tu sunt in a twisty error locis, omnibus. '});

  });

</script>

Puto hoc est satis tutum accessum, meaning that we should be able to find the field that we want and only the field we want. If you look at the HTML SharePoint is giving us, suus modi Nuntius:

<input
nomen="ctl00$m$g_bdb23c2c_fde7_495f_8676_69714a308d8e$ctl00$ctl04$ctl02$ctl00$ctl00$ctl04$ctl00$ctl00$TextField"
typus="text"
maxlength="255"
id="ctl00_m_g_bdb23c2c_fde7_495f_8676_69714a308d8e_ctl00_ctl04_ctl02_ctl00_ctl00_ctl04_ctl00_ctl00_TextField"
title="DefaultMeFieldNoSpaces"
genus="ms-long"
/>

"Title" stat ut a cognoscibilia et hopefully unicum attributum ad nobis recognoscendas speciei agmen ad quod volo ad assignare nostri arbitraria valorem.

This is a foundational concept. Setting a field in an arbitrary way like this isn’t going to win any awards. Autem, si vis ad magis interesting forma gradu effercio (quam omnes semper voluit, utique, post nos conpleveris lotis acetabula), similis mutare valorem "agro b" automatically fundatur in valorem "agro a", nos (Ego) opus discere haec.

Puto optimum forte ut realis utile valorem hic est per title, at least for text fields. There may be a better, more reliable approach. If I find it, Ego hoc update stipes. If you know a better way, placere relinquat comment.</finem>

</finem>

Scribet ad mea blog.

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

SharePoint Demonstratio: Leverage SharePoint ad aedifica a dui Lorem Application

Aliquam responsum

[Note: Quod ego volo, statim optatum exitum voluptate velit demonstratione, de qua plenam in re indicium, etc. This is actually the first time I’ve ever blogged about an event where I stand to benefit personally in this way.]

This web demonstration takes place Thursday, 06/04 ad 12:30 EDT, ending at 1:30PM EDT.

In cooperation with my excellent business partner, Ac integrata Systems Lorem Group (ISSG), I have been working to develop a vertical business application using SharePoint as the platform. In hoc, we’re building an application that serves the needs of manufacturers that make customized product for their customers. In these cases, a great deal of collaboration needs to take place between the customer and the manufacturer. There’s also a great deal of collaboration required between different groups within the manufacturer, including sales, engineering, research and development, legal and other groups.

The demo is going to show an application that facilitates that kind of collaboration, along with a discussion on how all of those collaboration bits need to integrate with a backend ERP system.

Denique, this isn’t going to be a SharePoint demo. This is a demonstration of a solution for a specific niche problem that happens to use SharePoint as the platform.

Ita, why would you bother to sign up and see this demo? I don’t expect too many readers of my blog to be all that interested in a solution for make-to-order manufacturers 🙂 Your take-away would be the concept itself – using SharePoint purely to deliver a business solution without regard to SharePoint itself.

Si tu interest, please sign up here(https://www323.livemeeting.com/lrs/8000043750/Registration.aspx?pageName=skmqfwbr5smmlx20).

</finem>

Scribet ad mea blog.

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

Te potest a frigus propugnavit SharePoint Designer, Manibus mortui

Aliquam responsum

My latest article is up at www.EndUserSharePoint.com. I wrote about SharePoint Designer, Finis finem vitae augue ut ipsum nulla lineamenta operam, ut ædificem et sufficientia ad ostendendam sequuntur circa hoc ferrum fidem.

Comments sunt magis interesting quam ipsum articulum.

Reprehendo eam.

</finem>

Scribet ad mea blog.

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

Technorati Tags: ,

Efficaciter Sequere Microsoft SharePoint (Alius) SharePoint Forums

2 Restituo

Ego secutus MSDN forums bene super anno, (et nusquam paene 2 Hie annis) and every now and then I hear from someone how “hard” it is to do that. I find it quite easy and thought I’d share my “technique”. This technique also works for www.endusersharepoint.com (http://www.endusersharepoint.com/STP).

Accipiens exemplum MSDN, Primum vexillum ad forum page ut quaestiones generales enim hic SharePoint Main Page: http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/threads

Vos should animadverto ut forums sunt statim mereantur RSS, ut ostensum:

image

Ive 'been usura Google Lector, ad gerenda mea RSS nutritor pro iamdudum (www.google.com / lector). I go there, add the RSS feed for the forum and now I’m getting all new forums posts via RSS. My Google feeds for SharePoint forums look like this:

image

Google praestat me a nice intuitu ad se dispositis:

image

Et tandem, Google dimittit me uti tincidunt ut scroll per Commentaires in via hac forums.

Velociter currit iustus focus in illis stationibus per possum sentio possum facere utile collationem.

Alerts close the loop. Updates to posts don’t come through RSS (sed opinor olim usi). Autem, si stipes responsio ad forum stipes, the forums alert me via email and IM that someone responded in turn. Aut, si autem non potest scire, quid utile alii ad collationem, EXERCITATIO in eam Explicite et possum rogare summis montibus cum alii respondent.

Nec minus in hora hebdomadam hanc, et in iudicio et consuetudine, varius tincidunt discere artes et shortcuts ut hoc fit secundum naturam,.

I use the exact same technique for End User SharePoint.Com’s “Stump the Panel” forums. This is their RSS feed: http://www.endusersharepoint.com/STP/rss/.

Forums formidolosum sunt via, fortasse optimum breve de recto usu, Morbi aliquet, quam praeclara in literis questus mundi, latissime, uses SharePoint. Give it a try!

</finem>

Scribet ad mea blog.

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

Technorati Tags:

Album enim consuetudo efficatiorem uti workflow auditing

2 Restituo

I’ve reorganized my life a bit and found some time to submit an article to www.endusersharepoint.com. My latest article is up here: Album enim consuetudo efficatiorem uti workflow auditing (http://www.endusersharepoint.com/?p=1658).

Hoc est foramen 'F:

SharePoint Designer workflow doesn’t give us a lot of visibility into what’s happening with our workflow solutions. Et, the visibility that we do get is hampered by a relatively poor interface and 60 day time window. Hoc 60 day window can be a major disappointment to new SharePoint Designer users because it’s not advertised by the tool itself. It’s not at all uncommon for someone to fire up SharePoint Designer, create a workflow solution that leverages the “Log To History List” action…

The problem is that after 60 diebus, any messages that you create this way are deleted from the workflow history list! After a bit of teeth gnashing and “what were they thinking?” arguments, the bottom line is this: it happens and it needs to happen. The question is, how can we get around it?

The official answer is to rely upon SharePoint’s built-in auditing feature. From an end user’s point of view, autem, that’s very weak in WSS and not much better in MOSS. Fortunate, we can still leverage the familiar SharePoint Designer tool to create a durable workflow history and audit trail which is an order of magnitude more useful to boot. Here’s how.

I describe how to create a more friendly and useful audit solution for declarative workflow created in SPD.

I was inspired to write this article from a recent project for a client that had developed nine technical SPD workflows in support of one logical business process. Assuming for now that nine is a reasonable number, it was certainly a challenge to debug it or view the overall status of the process in one simple view. Each of these separate technical workflows has its own independent workflow history list and that’s just not manageable. I was able to combine all of them into a single audit list using the technique I describe on the site.

Reprehendo eam.

</finem>

Scribet ad mea blog.

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

Causae Kalendario mutuo occurrant cum Bamboo SharePoint "inopinatum accidit error"

1 Respondere

Hodie, I’ve been working in an environment that uses a Bamboo calendar web part for some improved collaboration. This a standard medium/small farm with two load balanced WFEs, a "application server" Iudex enim InfoPath et bumastos et retro finem SQL.

The client installed some disaster recovery software onto one of the WFEs and that resulted in a broken WFE for a specific site in the site collection. Whenever load balancing pointed at the affected WFE and that site, users saw a largely blank white screen with the sentence “An unexpected error occurred”. No other info showed, Iustus, qui sententiam.

They asked me to look at it. I easily reproduced the problem and then added a ?contents=1 to the end of the URL. This is how I learned they were using the Bamboo web part. I went back to the page and now, Subito, eam ostendit mihi nice ordinate erroris nuntius:

image

Nescio quid esset aut quid ego facerem, nisi ut ostenderet appensione erroris nuntius ad imperium ?contents=1 bit of the query string.

Quod si ita est, ut probabiliter adipiscing verbo rarissimum, "Inopinatum accidit error" Antecedite adaugeo ?query = I ad contenta in eodem filo, et vide ubi ducentem.

</finem>

Scribet ad mea blog.

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

Technorati Tags: ,

Torminibus de Fenestra Ago Comment Imperium

2 Restituo

Ego sustulerunt retro spatia in Julii Windows Live 2007 as my blogging platform. For the most part, Certe ego non ullo desiderio et Microsoft extendit super tempus (si maxime exploratum de nova per accidens,).

My biggest complaint right now is blog spam. This person / propter (http://cid-82b0534bceed9881.profile.live.com/) (apud alios) frequently adds a lot of spam comments to my blog in the form of comments. MSFT added a nice feature to show “recent comments” so at least I can fairly quickly identify them (cum prius, Me ire in singulis separatim blog ingressu) and clean them up. It’s still time consuming.

Vellem:

  1. Facturum enim filtering melior MSFT quidam spam.
  2. Quod posset opponere populus ex peculiari adiceret comments.
  3. Deficientibus supra, I could more easily identify and delete spam. Right now, EGO postulo efficio is a comment ultricies et tarda, praesertim cum quidam spam robot persona / progressio addit 25 ad 50 comments in unum coetum.

Si vestri 'usura Fenestra Ago quod habent ad participes aliquid utile fallere, Curabitur sit gratus.

</endGripe>

Scribet ad mea blog.

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

Phaenomenon SharePoint Diei Persevero (plus, labi mea deck)

Aliquam responsum

I returned from Washington DC yesterday after attending the latest SharePoint sabbati. What a remarkable event! Continuing the tradition of other SP Saturday’s, it was very well run. The environment, altiore organizationem, Interfluxis, area venditor, terribili omnibus est cibus ....

Utique, the best part is the content and I don’t think anyone was disappointed.

It’s really quite amazing to me how so many people are rousing themselves out of bed early on a Saturday to go and listen to people talk about SharePoint for 8 hours 🙂 Amazing.

Odds are, there’s a SharePoint Saturday event coming your way and if there isn’t, why don’t you start one?

I presented at the conference with the tongue twisting title, “Using the SharePoint Platform to Build Vertical Business Applications.” You can get the presentation here: https://cid-1cc1edb3daa9b8aa.skydrive.live.com/browse.aspx/Public. It’s not my usual sort of presentation and I had fun with it. I’ll be giving this again in June at the North VA user group conference at the end of June.

</finem>

Scribet ad mea blog.

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

Technorati Tags: ,

Regimen est ipsum consilium Nimis

3 Restituo

Quod quidem expendendo tempus (aut mori, usquam) working out governance plans is because we want the SharePoint solution to be as effective as possible. We want good infrastructure and rules to keep it humming and safe in case of disaster. We want good security processes to both properly secure the environment but also make it reasonable to manage. We want a good information architecture that will stand the test of time, ideally managing to survive a major organizational change in the company.

To achieve that desirable objective, a governance document and plan can devolve into a bunch of “thou shall” and “thou shall not’s”, ut in:

  • Thou shall not create SharePoint security group; use AD instead.
  • Thou shall not create folders in document libraries; use content types and views instead.
  • Thou shall create all document content types based off a specific custom base type.
  • Thou shall not create an information taxonomy based off today’s company org chart.

“Thou shall” and “thou shall not” certainly have their place in the governance plan.

A more successful governance plan will also have a strong marketing angle. It should sell and justify itself to the maximum extent possible. A truly successful governance plan relies upon the voluntary cooperation of all SharePoint users. (There are fringe cases where community cooperation is not needed, such as when SharePoint is used by a very small number of tightly managed users; I’m sure you can think of others). If the user community doesn’t buy into your governance plan then it will be partially successful at best.

I use that word “buy” deliberately. The community will buy the governance plan if it’s fundamentally sound and you go to some effort to sell them on it. Selling leads to marketing and that’s why I think that a governance plan should be considered a marketing plan too. Convince your end users that they need to follow the governance plan and they will voluntarily follow it. If you can get a critical mass of people following the governance plan then the plan’s benefits follow and you’ll have a stronger environment for it.

</finem>

Scribet ad mea blog.

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

Solutio: Cras nec sociabitur componendis MUSCUS Audientia

Aliquam responsum

Imo linea: Si vis proprio uti profile in regula partum Audientiis, proprium esse manifestum "omnes."

I was working with a co-worker yesterday and he was building out a MOSS audience based on a custom user profile property in MOSS. In hoc, audientibus res nominatur "SITECD" et per conventionem, a recondit 3 moribus conueniebat. Quem definitum audientibus et plerumque dicitur, quod si "SITECD pares 'ABG", tunc comprehendunt quod Minutiae in auditorium.

Posuit et valorem unius user Quantcast cum compilavit in auditorium, but MOSS simply wouldn’t add that user. I noticed that the privacy setting for that profile was set to “me only” (maxime forma restrictiva) and I remembered reading somewhere that property profiles used in rules must be visible by “everyone”. He made that change and that solved the problem.

The really funny thing about this is that I “remembered” reading about this. It was nagging at me this morning for some reason and I realized that I had written a chapter in this book, MUSCUS Explained: Indicio immensi artifex demerguntur in Microsoft Muneris SharePoint Server 2007, et operui in hoc ipsum scripsi capitulo :). I would have thought that every word I wrote in that chapter would be seared into my memory.

Matt Morse scribit in hac specie pulchrum atque hic sum referenced in capitulo: http://blogs.pointbridge.com/Blogs/morse_matt/Pages/Post.aspx?_ID=50

</finem>Scribet ad mea blog.

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

Technorati Tags: ,