Quick u Easy: Uża jQuery Set Valur A Test Field dwar Formola SharePoint

I started playing around with jQuery yesterday. I’ve been wanting to do this for a long time, ever since Paul Grenier started writing his series about jQuery for End Users at the venerable 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 this scenario, I have created a custom list whose “new” form looks as shown:

image

This is the new form for a custom list with the default Title column and two list columns (not site columns; I don’t think it should make any difference).

The objective is to assign an arbitrary value to the field, “DefaultMeFieldNoSpaces” (you can tell I’m a bit of a coward with the “no spaces” thing going on, but I do spice it up at the end of this article).

This bit of jQuery worked for me:

<tip b'kitba ="text/javascript">

  $(funzjoni() {

    $("Input[title=DefaultMeFieldNoSpaces]").attr(
        {valur: 'You are in a twisty maze of passages, all alike.'});

  });

</iskrittura>

As I understand it this bit of jQuery is saying, “find me any input tag whose title = DefaultMeFieldNoSpaces. Imbagħad, set all of their values to a famous phrase from an old computer game.”

Since there will only be one field on the form with a title equal to “DefaultMeFieldNoSpaces” we are assured of assigning a value to that field and no other.

What about a field whose name has spaces in it? It’s nearly the same:

<tip b'kitba ="text/javascript">

  $(funzjoni() {
     $("Input[title=Assign Field With Space]").attr(
        {valur: 'You are in a twisty maze of passages, all alike.'});

  });

</iskrittura>

I think this is a fairly safe approach, 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, it’s sort of messy:

<input
isem="ctl00$m$g_bdb23c2c_fde7_495f_8676_69714a308d8e$ctl00$ctl04$ctl02$ctl00$ctl00$ctl04$ctl00$ctl00$TextField"
tip="text"
maxlength="255"
id="ctl00_m_g_bdb23c2c_fde7_495f_8676_69714a308d8e_ctl00_ctl04_ctl02_ctl00_ctl00_ctl04_ctl00_ctl00_TextField"
titolu="DefaultMeFieldNoSpaces"
klassi="ms-long"
/>

“title” stands out as a recognizable and hopefully unique attribute to help us identify the specific column to which we want to assign our arbitrary value.

This is a foundational concept. Setting a field in an arbitrary way like this isn’t going to win any awards. Madankollu, if we want to do more interesting form level stuff (which all of us always want to do, tal-kors, right after we finish washing the dishes), like change the value of “field b” automatically based on the value of “field a”, aħna (I) need to learn these things.

I think our best chance to get a real useful value here is via the title, at least for text fields. There may be a better, more reliable approach. If I find it, I ser taġġorna din il-kariga. If you know a better way, jekk jogħġbok leave kumment.</aħħar>

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Dimostrazzjoni SharePoint: SharePoint Leverage Tibni Applikazzjoni Business Vertikali

[Innota: Irrid ngħid mill-ewwel li jien jkollhom interess finanzjarju fir-riżultat mixtieq ta 'din id-dimostrazzjoni, li nsemmi fl-interess tal-iżvelar sħiħ, eċċ. This is actually the first time I’ve ever blogged about an event where I stand to benefit personally in this way.]

Din id-dimostrazzjoni web iseħħ il-Ħamis, 06/04 fil 12:30 EDT, li jispiċċa mill- 1:30PM EDT.

F'kooperazzjoni mal-partner tiegħi negozju eċċellenti, Sistemi integrati u Group Services (ISSG), I have been working to develop a vertical business application using SharePoint as the platform. F'dan il-każ, 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, inkluż il-bejgħ, inġinerija, riċerka u żvilupp, gruppi legali u oħrajn.

Il-demo se juru applikazzjoni li jiffaċilita dan it-tip ta 'kollaborazzjoni, flimkien ma 'diskussjoni dwar kif kollha ta' dawk bits kollaborazzjoni jeħtieġu li jintegraw ma 'sistema ERP backend.

Fl-aħħar nett, 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.

Allura, għaliex kieku inti jolqot biex jiffirmaw u tara dan 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.

Jekk int interessat, jekk jogħġbok jiffirmaw hawn(https://www323.livemeeting.com/lrs/8000043750/Registration.aspx?pageName=skmqfwbr5smmlx20).

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Tista PRY Designer SharePoint Mill My Cold, Idejn Mejjet

My latest article is up at www.EndUserSharePoint.com. I wrote about SharePoint Designer, Utenti finali u l-punti prinċipali ta 'strateġija li l-utenti finali tista' tipprova u jsegwu sabiex juru l-kompetenza u tinbena l-fiduċja madwar din l-għodda.

Il-kummenti huma aktar interessanti mill-oġġett innifsu.

Iċċekkjaha.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Effiċjenti Segwi Microsoft SharePoint (u oħrajn) SharePoint Forums

I ġew wara forums MSDN għal iktar minn sena (u possibilment kważi 2 snin f'dan il-punt) 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).

Teħid MSDN bħala eżempju, I l-ewwel imorru għall-paġna forum standard bħall-Mistoqsijiet ġenerali għall-paġna prinċipali SharePoint hawn: http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/threads

Għandek dritt bogħod tinnota li l-forums huma RSS ppermettiet, kif muri:

image

I kont qed tuża Google Reader għall-ġestjoni RSS feeds tiegħi għal żmien twil issa (www.google.com / qarrej). 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 jipprovdi me ħsieb sbieħ ta 'l-istazzjonar innifsu:

image

U finalment, Google tikri me jużaw il-keyboard biex iscroll permezz l-assenjazzjonijiet fil-fora b'dan il-mod.

I tista 'malajr scan permezz postijiet u tiffoka biss fuq dawk inħoss I jistgħu jagħmlu kontribut utli.

Alerts close the loop. Updates to posts don’t come through RSS (għalkemm naħseb huma użati għal żmien twil ilu). Madankollu, jekk I post risposta għal forum kollokament, the forums alert me via email and IM that someone responded in turn. Jew, jekk I ma jistgħux jagħmlu kontribut utli imma nixtieq li tkun taf dak li oħrajn jgħidu, I jistgħu drill fis dan u titlobx espliċitament allerti meta oħrajn do jirrispondu.

Fl-siegħa jew inqas inti tista 'dan il-proċess up u u fil-ġimgħa ta' użu regolari, jitgħallmu l-tricks varji u shortcuts tastiera sabiex din issir tieni natura.

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 huma mod biża, possibilment l-aħjar mod qasir ta 'esperjenza personali diretta, ta 'tagħlim l-prodott u jkollna stħarriġ sbieħ ta' kif id-dinja, in ġenerali, uses SharePoint. Give it a try!

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Tags:

Użu Listi Custom għall Verifika Workflow Iktar Effettiva

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: Użu Listi Custom għall Verifika Workflow Iktar Effettiva (http://www.endusersharepoint.com/?p=1658).

Dan huwa graff il-ftuħ ":

SharePoint Designer workflow doesn’t give us a lot of visibility into what’s happening with our workflow solutions. U, the visibility that we do get is hampered by a relatively poor interface and 60 day time window. Dan 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 jiem, 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. Il-kwistjoni hija, 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, madankollu, that’s very weak in WSS and not much better in MOSS. Fortunatament, 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.

Iċċekkjaha.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Bambu Kalendarju Interazzjoni ma SharePoint Causes "żball mhux mistennija ġara"

Illum, 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 "server applikazzjoni" għal indiċjar u InfoPath u SQL back aħħar raggruppat.

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, biss li sentenza.

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, f'daqqa, dan wera lili messaġġ ta 'żball sbieħ ordnat:

image

I do not know dak li kien qed jiġri jew dak li għamilt biex jiksbu l-messaġġ ta 'żball kkontrollata li juri għajr jpoġġu l- ?contents=1 bit of the query string.

Din hija probabbilment każ tarf rari ħafna iżda jekk ikollok dak il-messaġġ, "Żball mhux mistennija ġara" jimxi 'l quddiem u żid ?kontenut = 1 sa l-sekwenza mistoqsija u ara fejn dan iwassal.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Griping dwar Windows Live Kontroll Kumment

I picked windows live spaces back in July of 2007 as my blogging platform. For the most part, I don’t have any regrets and Microsoft certainly extends it over time (though I mainly find out about new features by accident).

My biggest complaint right now is blog spam. This person / account (http://cid-82b0534bceed9881.profile.live.com/) (among others) 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 (whereas before, I had to go into each blog entry separately) and clean them up. It’s still time consuming.

I wish that:

  1. MSFT would put some better filtering for spam.
  2. That I could block specific people from adding comments.
  3. Failing the above, I could more easily identify and delete spam. Right now, I need to do it comment by comment and it’s slow, especially when some spam robot person/program adds 25 li 50 comments in one session.

If you’re a windows live user and have some useful tricks to share, I’d be grateful.

</endGripe>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

SharePoint is-Sibt Phenomenon Ikompli (plus, gverta slide tiegħi)

I lura minn Washington DC bieraħ wara li jattendu l-aħħar SharePoint is-Sibt. What a remarkable event! Continuing the tradition of other SP Saturday’s, it was very well run. The environment, l-organizzazzjoni ġenerali, l-fluss, żona bejjiegħ, ikel ... kollha ta 'dan kien terrific.

Of course, l-aħjar parti huwa l-kontenut u ma naħsibx xi ħadd kien diżappuntat.

Huwa verament pjuttost aqwa lili kif tant nies huma rousing infushom mis-sodda kmieni nhar ta 'Sibt li jmorru u jisimgħu nies jitkellmu dwar SharePoint għall 8 hours 🙂 Amazing.

Odds huma, hemm avveniment is-Sibt SharePoint ġejjin mod tiegħek u jekk ma jkunx hemm, għaliex ma inti tibda waħda?

I ippreżentati fil-konferenza bit-titolu brim ilsien, “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.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Il-governanza hija Pjan Marketing Too

Ir-raġuni aħna jqattgħu daqstant ħin (jew jekk, xorta waħda) 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.

Biex jinkiseb dan l-għan mixtieq, dokument governanza u pjan jista jiddevolvu fis mazz ta '"thou għandu" u "thou m'għandhomx tal-", kif fil-:

  • Thou m'għandhomx joħolqu grupp sigurtà SharePoint; użu AD minflok.
  • Thou m'għandhomx joħolqu folders fil-libreriji dokument; użu kontenut ta 'tipi u l-fehmiet minflok.
  • Thou għandhom joħolqu tipi kollha ta 'kontenut dokument bbażata off tip speċifiku bażi custom.
  • Thou m'għandhomx joħolqu tassonomija informazzjoni bbażata off chart lum org kumpanija.

"Thou għandhom" u "thou m'għandhomx" ċertament għandhom il-post tagħhom fil-pjan ta 'governanza.

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. (Hemm każijiet marġinali fejn il-kooperazzjoni Komunitarja mhux meħtieġa, bħal meta SharePoint hija użata minn numru żgħir ħafna ta 'utenti ġestiti sewwa; 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.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Soluzzjoni: Kumpilazzjoni Audience MOSS Iżżid Nru Membri ġodda

Bottom line: jekk inti tixtieq li tuża proprjetà profil f'regola għall-ħolqien udjenzi, il-propjetà għandha tkun viżibbli għal "kulħadd."

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. F'dan il-każ, l-proprjetà udjenza huwa msemmi "SITECD" u permezz tal-konvenzjoni, ħwienet 3 Kodiċi karattru. Huwa kien iddefinixxa l-udjenza u regola li qal li jekk "SITECD ugwali" ABG "", mbagħad jinkludi li l-profil utent fl-udjenza.

Huwa twaqqaf profil utent wieħed ma 'dak il-valur u kkompilata l-udjenza, but MOSS simply wouldn’t add that user. I noticed that the privacy setting for that profile was set to “me only” (l-aktar forma restrittivi) 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, MOSS Explained: An Information Worker’s Deep Dive into Microsoft Office SharePoint Server 2007, and that I covered this point in the very chapter I wrote :). I would have thought that every word I wrote in that chapter would be seared into my memory.

Matt Morse writes this up in beautiful detail here and I referenced it in the chapter: http://blogs.pointbridge.com/Blogs/morse_matt/Pages/Post.aspx?_ID=50

</aħħar>Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin