Haraka na Easy: Kutumia jQuery ili Kuweka Thamani Shamba Nakala ya juu ya kidato SharePoint

5 majibu

I started playing around with jQuery yesterday. I’ve been wanting to do this for a long time, ever since Paulo 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:

<script aina ="text/javascript">

  $(kazi() {

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

  });

</script>

As I understand it this bit of jQuery is saying, “find me any input tag whose title = DefaultMeFieldNoSpaces. Kisha, 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:

<script aina ="text/javascript">

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

  });

</script>

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:

<pembejeo
jina="ctl00$m$g_bdb23c2c_fde7_495f_8676_69714a308d8e$ctl00$ctl04$ctl02$ctl00$ctl00$ctl04$ctl00$ctl00$TextField"
aina="text"
maxlength="255"
id="ctl00_m_g_bdb23c2c_fde7_495f_8676_69714a308d8e_ctl00_ctl04_ctl02_ctl00_ctl00_ctl04_ctl00_ctl00_TextField"
cheo="DefaultMeFieldNoSpaces"
darasani="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. Hata hivyo, if we want to do more interesting form level stuff (which all of us always want to do, bila shaka, right after we finish washing the dishes), like change the value of “field b” automatically based on the value of “field a”, sisi (Mimi) 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, Mimi itabidi update hii post. If you know a better way, tafadhali acha maoni.</mwisho>

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

SharePoint Maandamano: Kujiinua SharePoint Kujenga Wima Biashara Maombi

Acha reply

[Kumbuka: Nataka mara moja kusema kwamba nina maslahi ya kifedha katika matokeo ya taka ya maandamano haya, ambayo mimi kutaja kwa maslahi ya kutoa taarifa kamili, nk. This is actually the first time I’ve ever blogged about an event where I stand to benefit personally in this way.]

Maandamano haya mtandao unafanyika Alhamisi, 06/04 katika 12:30 EDT, kuishia katika 1:30PM EDT.

Katika ushirikiano na mpenzi wangu bora ya biashara, Jumuishi Systems na Huduma Group (ISSG), I have been working to develop a vertical business application using SharePoint as the platform. Katika kesi hiyo, 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, ikiwa ni pamoja na mauzo ya, uhandisi, utafiti na maendeleo, kisheria na makundi mengine ya.

demo ni kwenda kuonyesha maombi kwamba kuwezesha kwamba aina ya ushirikiano, pamoja na majadiliano juu ya jinsi ya bits wale kushirikiana haja ya kuunganisha pamoja na mfumo backend ERP.

Mwisho, 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.

Hivyo, kwa nini wewe bother kwa ishara ya juu na kuona demo? Sitarajii wasomaji wengi wa blog yangu kwa kuwa kwamba nia zote katika ufumbuzi kwa wazalishaji kufanya-kwa-ili 🙂 yako kuchukua-mbali itakuwa dhana yenyewe - kwa kutumia SharePoint rena kutoa biashara ufumbuzi bila ya kujali SharePoint yenyewe.

Kama wewe ni nia, tafadhali jisajili hapa(https://www323.livemeeting.com/lrs/8000043750/Registration.aspx?pageName=skmqfwbr5smmlx20).

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Unaweza tafiti SharePoint Designer Kutoka baridi yangu, Wafu Mikono

Acha reply

Makala yangu ya karibuni ni hadi saa www.EndUserSharePoint.com. I wrote about SharePoint Designer, Watumiaji wa mwisho na muhtasari wa mkakati kwamba Mwisho Watumiaji wanaweza kujaribu na kufuata ili kuonyesha umahiri na kujenga imani kuzunguka chombo hiki.

maoni ni ya kuvutia zaidi kuliko makala yenyewe.

Kuangalia ni nje.

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Ufanisi Kufuata Microsoft SharePoint (na nyingine) SharePoint Forums

2 majibu

Nimekuwa kufuatia vikao MSDN kwa vizuri zaidi ya mwaka (na uwezekano wa karibu 2 miaka katika hatua hii) 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).

Kuchukua MSDN kama mfano, Mimi kwanza kwenda kwenye ukurasa wa kiwango jukwaa kama vile Maswali Mkuu kwa ajili ya ukurasa SharePoint kuu hapa: http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/threads

Unapaswa haki mbali taarifa kwamba vikao ni RSS kuwezeshwa, kama inavyoonekana:

image

Nimekuwa kutumia Google Reader kwa ajili ya kusimamia yangu RSS feeds kwa muda mrefu sasa (www.google.com / msomaji). 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 inatoa mimi mtazamo mzuri wa posting yenyewe:

image

Na hatimaye, Google lets mimi kutumia keyboard na kitabu kupitia matangazo katika vikao kwa njia hii.

Siwezi haraka Scan kupitia posts na mkazo tu kwa wale nahisi naweza kutoa mchango muhimu.

Alerts close the loop. Updates to posts don’t come through RSS (ingawa nadhani wao kutumika muda mrefu uliopita). Hata hivyo, kama mimi baada ya kukabiliana na jukwaa posting, the forums alert me via email and IM that someone responded in turn. Au, kama siwezi kutoa mchango muhimu lakini nataka kujua nini wengine kusema, Siwezi kuchimba ndani yake na kupanga kuomba alerts wakati wengine kufanya kujibu.

Katika saa au chini unaweza kuweka mchakato huu juu na na katika wiki ya matumizi ya kawaida, kujifunza mbinu mbalimbali na njia za mkato keyboard hivyo kwamba hii inakuwa asili ya pili.

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/.

Vikao ni njia ya kutisha, pengine njia bora ya muda wa uzoefu wa moja kwa moja binafsi, ya kujifunza bidhaa na kupata utafiti mzuri wa dunia jinsi, saa kubwa, uses SharePoint. Give it a try!

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Tags technorati:

Kutumia Orodha Desturi kwa Ukaguzi wa Ufanisi Zaidi Workflow

2 majibu

Nimekuwa utaratibu wa maisha yangu kidogo na kupatikana muda wa kuwasilisha makala kwa www.endusersharepoint.com. My latest article is up here: Kutumia Orodha Desturi kwa Ukaguzi wa Ufanisi Zaidi Workflow (http://www.endusersharepoint.com/?p=1658).

Hii ni graph ufunguzi ':

SharePoint Designer workflow doesn’t give us a lot of visibility into what’s happening with our workflow solutions. Na, kujulikana kwamba sisi kufanya kupata inakwamishwa na interface duni kiasi na 60 day time window. Hii 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, kujenga ufumbuzi workflow kwamba leverages "Fungua Ili Historia Orodha" hatua ...

Tatizo ni kwamba baada ya 60 siku, ujumbe wowote kwamba kujenga njia hii ni ilifutwa kutoka kwenye orodha workflow historia! After a bit of teeth gnashing and “what were they thinking?"Hoja, line ya chini ni hii: it happens and it needs to happen. Swali ni, 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, hata hivyo, that’s very weak in WSS and not much better in MOSS. Fortunately, 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.

Kuangalia ni nje.

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Mianzi kalenda Kushirikiana na SharePoint Sababu "Hitilafu isiyotarajiwa ilitokea"

1 Kujibu

Leo, 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, "Maombi server" kwa Indexing na InfoPath na mashada SQL mwisho ya nyuma.

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, just that sentence.

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, suddenly, it showed me a nice orderly error message:

image

I don’t know what was happening or what I did to get the controlled error message to display other than appending the ?contents=1 bit of the query string.

This is probably a very rare edge case but if you get that message, “An unexpected error occurred” go ahead and add ?contents=1 to the query string and see where that leads.

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Tags technorati: ,

Griping kuhusu Windows Live maoni Udhibiti

2 majibu

Mimi ilichukua madirisha nafasi ya kuishi nyuma katika Julai ya 2007 as my blogging platform. For the most part, Mimi hawana majuto na Microsoft hakika inaenea zaidi ya muda (ingawa mimi hasa kujua kuhusu makala mpya kwa ajali).

My biggest complaint right now is blog spam. This person / akaunti (http://cid-82b0534bceed9881.profile.live.com/) (miongoni mwa wengine) 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 (ambapo kabla ya, Mimi nilikuwa na kwenda katika kila kuingia blog tofauti) and clean them up. It’s still time consuming.

Napenda kwamba:

  1. MSFT bila kuweka baadhi ya kuchuja bora kwa spam.
  2. Kwamba mimi naweza kuzuia watu maalum kutoka kuongeza maoni.
  3. Kushindwa hapo juu, I could more easily identify and delete spam. Right now, Mimi haja ya kufanya hivyo maoni na maoni na ni mwepesi, hasa wakati baadhi spam robot mtu / mpango anaongeza 25 kwa 50 maoni katika kikao moja.

Kama wewe ni mtumiaji madirisha kuishi na kuwa na baadhi ya mbinu muhimu ya kushiriki, Ningependa kushukuru.

</endGripe>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

SharePoint Jumamosi uzushi inaendelea (zaidi, slide yangu staha)

Acha reply

Mimi kurudi kutoka Washington DC jana baada ya kuhudhuria karibuni SharePoint Jumamosi. What a remarkable event! Continuing the tradition of other SP Saturday’s, it was very well run. The environment, shirika kwa ujumla, mtiririko, muuzaji eneo, chakula ... wote wa ilikuwa ni kali.

Bila shaka, sehemu bora ni maudhui na sidhani mtu yeyote alisikitika.

Ni kweli kabisa ajabu kwangu jinsi watu wengi ni kuibua wenyewe nje ya kitanda mapema Jumamosi kwenda na kusikiliza mazungumzo ya watu kuhusu SharePoint kwa 8 masaa 🙂 Amazing.

Ni tabia mbaya, kuna SharePoint Jumamosi tukio kuja njia yako na kama kuna, kwa nini wewe kuanza moja?

Mimi kuwasilishwa katika mkutano na cheo ulimi wakasokota, “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.

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Utawala ni Mpango wa Masoko Too

3 majibu

Sababu ya sisi kutumia muda sana (au lazima, anyway) 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”, kama katika:

  • Thou shall not create SharePoint security group; use AD instead.
  • Thou shall not create folders in document libraries; kutumia aina maudhui na maoni badala.
  • Wewe itakuwa kujenga kila aina maudhui ya hati ya msingi mbali maalum aina desturi msingi.
  • Wewe wala kujenga Jamii habari ya msingi mbali chati kampuni ya leo org.

"Wewe atakuwa" na "wewe wala" hakika kuwa na nafasi zao katika mpango wa utawala.

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. (Kuna pindo kesi ambapo ushirikiano wa jamii si zinahitajika, kama vile wakati SharePoint hutumiwa na idadi ndogo sana ya watumiaji kukazwa imeweza; Mimi nina uhakika unaweza kufikiria wengine). 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.

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Ufumbuzi: Kuandaa MOSS Audience Anaongeza Wanachama No New

Acha reply

Bottom line: kama unataka kutumia mali profile katika utawala kwa ajili ya kujenga watazamaji, mali lazima kuwa wazi "kwa kila mtu."

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. Katika kesi hiyo, mali watazamaji ni jina "SITECD" na kwa mkataba, maduka ya 3 tabia ya kanuni. Alikuwa inavyoelezwa watazamaji na utawala kwamba alisema kwamba kama "SITECD sawa 'ABG'", basi ni pamoja na kwamba user profile katika watazamaji.

Yeye kuanzisha single user profile na thamani ya kwamba na ulioandaliwa watazamaji, but MOSS simply wouldn’t add that user. I noticed that the privacy setting for that profile was set to “me only” (fomu ya vikwazo) 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: Habari mfanyakazi ya Deep Kupiga mbizi katika Ofisi ya Microsoft SharePoint Server 2007, na kwamba mimi kufunikwa hatua hii katika sura sana niliandika :). I would have thought that every word I wrote in that chapter would be seared into my memory.

Matt Morse anaandika hii up kwa undani nzuri hapa na mimi ni inatazamwa katika sura: http://blogs.pointbridge.com/Blogs/morse_matt/Pages/Post.aspx?_ID=50

</mwisho>Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Tags technorati: ,