SharePoint duka Majadiliano Open Q&Alhamisi Kikao 08/13 @ 12:30 PM EDT

Arcovis itakuwa mwenyeji wetu wa pili "SharePoint duka Majadiliano" kikao hiki Alhamisi saa 12:30 PM EDT. Show up with your SharePoint questions and we’ll do our best to entertain you with banjo jokes, smart but harmless put-downs of our fellow panelists and maybe even answer a question or two. This week’s “official” panel includes yours truly, yangu Arcovis washirika (Natalya Voskresenskaya na Harry Jones) na Laura Rodgers (ya Twitter & EndUserSharePoint umaarufu). Bob fox threatened to join too, but I don’t take that too seriously. Last time, sisi alikuwa na kiwango kikubwa cha ushiriki watazamaji ambayo blurred mstari kati panelists na waliohudhuria na mimi kutarajia huo kitatokea Alhamisi.

Tukio hili ni ushirikiano kufadhiliwa na Systems Integrated na Huduma Group (www.issgroup.net).

Tafadhali kujiandikisha hapa: https://www323.livemeeting.com/lrs/8000043750/Registration.aspx?pageName=9xrzxfs9x34sb0sm

Kama una maswali kwamba Ningependa sisi kuchukua, just dial into the call and ask it. If you want us to think about it first, tutumie barua pepe au kuacha maoni hapa.

Tazama wewe hapo!

</mwisho>

Kujiunga na blog yangu.

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

Kabla zilizopo Masharti: SharePoint Alert Matukio na Uokoaji (?)

One of my clients worked with a previous contractor to build out a small but useful HR application for the enterprise. That contractor used SharePoint Designer to implement the workflow portion of the solution. It’s a bit of a mess. Kwa mfano, there are nine SPD workflows in support of a single logical workflow process and up to five of them may fire simultaneously at any given time given the right conditions. It’s not easy to debug 🙂

Mteja wangu ana idadi ya mahitaji bado-bora, one of which is to generally provide more context when the system sends out email alerts – both in the email itself as well as associated task forms. As SPD workflow implementers know, the “collect data from user” SPD action actually creates a task with a custom content type. When we use that action, we don’t get to specify much. We can prompt for some values (e.g. "Kupitisha" au "kukataa") and we can specify a hard coded value in the title and description. That’s about it.

Mahitaji ya mteja wangu ni mara mbili:

  1. Wakati SharePoint zituma barua pepe kuhusu zoezi kazi, ni pamoja na mengi ya habari kuhusu kazi katika mwili email.
  2. Muhimu zaidi, kwa mbali – wakati mtumiaji Clicks juu ya kiungo kazi katika barua pepe, the task form should have all the information the approver needs in order to make his/her approve or deny decision. Right now, the manager needs to click on the item link itself to drill down into the underlying details and no one likes that. You have to click in the email. Then you need to click a sort of obscure link on the task item. Then you can look at the underlying data (Fomu InfoPath katika kesi hii). Then you click back/back, nk. Everyone hates it.

Nimekuwa kurithi hii kiasi fulani messy ufumbuzi wa kiufundi na mimi nataka kufanya mabadiliko katika njia angalau intrusive inawezekana.

The approach I’m taking right now is to create a custom alert template. Unaweza kusoma juu ya kwamba hapa. The flow works like this:

  • SPD workflow anaendesha.
  • Katika hatua nyingine, ni inateua kazi na meneja.
  • SharePoint system automatically sends out an alert to that manager. This is not part of the SPD workflow but rather “what SharePoint does.” (Timer SharePoint huduma, Naamini).
  • desturi handler tahadhari ni kutenguliwa katika neema ya mchakato kiwango tahadhari (kufuata sheria ya uchawi kama ilivyoelezwa katika makala hapo juu inatazamwa).
  • Wakati macho yangu handler desturi anaendesha, it generates a beautiful email. Muhimu zaidi, tangu ina kazi katika mkono, pia decorates kazi halisi na taarifa ya mazingira yote muhimu ili kukidhi mahitaji ya biashara.
  • mtumiaji anapata barua pepe na ni kamili ya habari muhimu muktadha.
  • Mtumiaji Clicks juu ya kiungo kazi na kazi yenyewe ni kamili ya habari muhimu muktadha.
  • Kila mtu anakwenda nyumbani kuwa na tikiti maji na ice cream.

I did a quick POC and it works well in a lab environment. I get my custom email alert as expected. I also get to update the task description and title itself.

tu gumu kidogo, hadi sasa, ni kuepuka hali ambapo updates tahadhari bidhaa, triggering another alert. This doesn’t worry me.

Inaonekana kuahidi hadi sasa ...

The great thing about this is that I don’t need to muck about with any of the existing SPD workflows. They are blissfully unaware that an alert handler is “IIZ Runnin IN DA BAKGROUND, DECORATIN teh KAZI ORODHA WIF moar MAELEZO".

</mwisho>

Kujiunga na blog yangu.

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

Kuishi SharePoint Q&Alhamisi Kikao 07/30/09 @ 12:30 EDT kukomesha 1:30PM EDT

Mwisho: The format for this is basically a conference call with a couple of PPT slides to set the stage. We have a SharePoint environment on stand by to fire up in case it helps out, but this is mainly people talking out loud. There will be opportunities for follow up by email.

Tukirudi kwenye mkutano yangu ya kwanza kabisa SharePoint, tu zaidi ya mwaka mmoja uliopita, Nimekuwa akampiga kwa jinsi kali Q kuishi&A session can be. The conference organizers had put together a sort of ad hoc group of “experts” (i.e. watu ambao walikuwa wanazurura na walikuwa na hofu ya kuangalia silly juu ya hatua) to answer any questions that came from the audience in the room. It was in my head back then, na mara kwa mara tangu wakati huo, to host a similar session but do it on line and the phone. I don’t think it can be as good as an in-person Q&kikao, lakini nadhani inaweza kuwa pretty baridi.

Mimi hatimaye got karibu yake na Alhamisi ijayo, 07/30, yangu kampuni (Arcovis) na mpenzi biashara, Jumuishi Systems na Huduma za kundi, itakuwa mwenyeji Q&A like that. I’m hoping to do these regularly, as often as weekly.

Kikao hiki uzinduzi pengine kuwa kidogo bumpy, lakini dhana hii ni:

  • Kama una maswali ambayo ungependa kuwa akajibu wakati wa kikao, tu show up na kuuliza.
  • Kama unataka, unaweza email swali mapema.

Tuna mpango wa kutumia nusu ya kwanza ya Q&juu ya maswali yaliyopelekwa na kisha kufungua it up na kitu chochote kwamba mtu anauliza baada ya kuwa.

kikao unafanyika Alhamisi, 07/30 kuanzia saa 12:30 na kuishia katika 1:30 PM EDT.

Kama wewe ni nia, kindly kujiandikisha hapa: https://www323.livemeeting.com/lrs/8000043750/Registration.aspx?pageName=pxlsd9fpsm2md7h9

The panel will include me and other SharePoint luminaries. You’ll have to sign up to find out who they are 🙂

Kama Ningependa kuwa mmoja wa mianga wale kwa Q baadaye&kikao, napenda kujua.

</mwisho>

Kujiunga na blog yangu.

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

Tags technorati:

Embed Vidokezo Developer Ndani ya Fomu yako InfoPath

Mimi bado wanaishi katika dunia InfoPath Fomu na mimi zinahitajika kufanya moja ya mabadiliko hayo "ndogo" kwa ajili ya kwamba, kwa bahati mbaya, breaks a naming convention I adopted with it two weeks ago. Mimi nilidhani, "Mtu ni kwenda kuangalia kitu mwaka huu kutoka sasa na kusema, 'Je, Paulo alikuwa kufikiri? By Jove, kumtaja mkataba wake haina mantiki!"

Nilitambua kwamba inaweza kujenga mtazamo juu ya fomu kwa ajili ya hii na kisha, mara nyingine tena, realized that I could have been doing something like this all along. I added a “Developer Notes” view to the InfoPath form as such:

image

Nimekuwa kimeundwa fomu ili watumiaji hawawezi kupata maoni kuwa na hivyo, it’s only visible with the InfoPath client in design view. Now I feel a little inoculated against some future unknown developer looking at my form and thinking bad thoughts about me. Phew!

</mwisho>

Kujiunga na blog yangu.

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

Tags technorati:

Kusimamia Views InfoPath

Mimi kuonekana kwenda kwa njia ya awamu InfoPath ambapo, nje ya bluu, I’m crafting a bunch of forms. My fingers learn how to use the tool well and then I go through nine month drought and have to learn it all over again.

Mimi nina katikati ya awamu InfoPath na mimi nina kujenga aina InfoPath na mengi ya maoni. Jambo moja pengine taarifa ni kwamba InfoPath 2007 client shows views in alphabetical order. This is a real nuisance some times. My best technique these days is to prepend a number to the view name so that they always show in the order I want, kama inavyoonyeshwa hapa:

image

I wish I had been doing this all along.

</mwisho>

Kujiunga na blog yangu.

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

Tags technorati:

InfoPath kidato huduma za, Hutengeneza Uthibitishaji Based (FBA) na kipekee Picha Majina

Nimekuwa kazi juu ya InfoPath baadhi hutengeneza wiki hii katika MOSS katika mazingira FBA na kujifunza, wakati mimi akaenda kupeleka fomu kwa mazingira ya uzalishaji na ukanda FBA kwamba jina la mtumiaji() function function does not work. I was using it to generate unique file names.

Vizuri, kwamba kazi hana kazi katika mazingira FBA (angalau, si nje ya boksi). Na, juu ya tafakari, kutumia jina katika njia nilipanga bila kuwa na uhakika kipekee faili jina katika tukio lolote.

Ufumbuzi yangu ilikuwa kutumia sasa() function and a rule that fires on loading of the form. I assign the file name to data element when it’s blank:

image

image

The advantage of this approach is that the file name is set only once. (Mimi si kuonyesha kuwa katika risasi screen, lakini kuweka hali ya juu ya utawala kwa moto tu wakati "myFilename" ni tupu). I used to set the file name at the data source level. Typically, Napenda kufanya kitu (mbaya) kama hii:

image

tatizo na kwamba ni kwamba kama mtumiaji kufungua fomu Jumatatu na B mtumiaji hulibadilisha Jumanne, kuishia na aina mbili tofauti tangu mbili watumiaji mbalimbali kuokolewa ni pamoja na majina tofauti ya mtumiaji.

Hivyo, kama annoying kama FBA unaweza kuwa kwa ujumla na kwa InfoPath hasa, amenifanya kufikiria upya ndogo lakini kwa kweli muhimu ya kiufundi undani na mbinu kwamba mimi bila kuwa na kosa vinginevyo!

</mwisho>

Kujiunga na blog yangu.

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

Tags technorati:

Kupata SharePoint Views Library Orodha / Document Inaonekana (aina ya) Ikiwezekana na jQuery

Hii ni baada ya mwingine katika wangu inayoendelea mfululizo ya jinsi ya kutumia jQuery na SharePoint.
Kama unataka kujifunza zaidi kuhusu jQuery, Mimi sana kupendekeza: jQuery katika Action na kubeba Bibeault na Yehuda Katz.

Moja ya mambo ya kwanza nilidhani, mara moja Nilianza kucheza karibu na jQuery, was whether we could use it to secure a SharePoint view. The answer is “no” (au angalau, Mimi si wakidai inawezekana). Hata hivyo, it is certainly possible to make it difficult for people to see a particular view.

I started with my sandbox environment when working on this. I wrote about that environment here: Haraka na Easy: Kujenga jQuery yako mwenyewe Sandbox kwa SharePoint.

Na "kupata" maoni, kufuata hatua hizi:

  1. Create a view you want to secure. I did that and called it “Secured View”.

    Hii ni nini inaonekana kama wakati ni si "kuulinda":

    image

  2. Kuongeza mhariri maudhui ya mtandao sehemu ya ukurasa mtazamo wa kutumia hila ilivyoelezwa katika makala Sandbox (i.e. kuongeza "PageView = Shared&ToolPaneView = 2 "ya URL).
  3. Figure out your SharePoint _spUserId by following these crazy steps, amini au si:
    1. Kuingia katika SharePoint mazingira yako.
    2. Katika anuani ya shamba kivinjari cha, aina: "Javascript:tahadhari(_spUserId ").
    3. Kurekodi matokeo (ni "13" katika kesi yangu).

      image

  4. Kuongeza javascript zifuatazo CEWP yako katika mtazamo wa kanuni:

    <script
        "text/javascript"
        src ="../../jQuery Library/jquery-1.3.2.min.js">
    </script>
    
    <script aina ="text/javascript">
      $(kazi() {
    
        tahadhari(_spUserId);
    
        var theSecuredView = $('Iframe[FilterLink * = Secured% 20View]');
    
        kama ((theSecuredView.length > 0) && (_spUserId == 13))
          $('Iframe[FilterLink * = Secured% 20View]').mzazi().mzazi().mzazi().html("<tr Bgcolor = nyekundu><td>Hakuna mtazamo kwa wewe!</td></tr>");
      });
    
    </script>
    

Nimekuwa pamoja na kwamba tahadhari(_spUserId) mstari katika huko kuonyesha jinsi hii si kweli "kupata" maoni, but simply making it more difficult to see. More on that in a moment.

Kimsingi, jQuery is looking for an iFrame on the page who has an attribute that contains “Secured View” in its value. Once it finds it, we check to see if the current user is “13”. If it is, sisi kutembea hadi DOM kwa <TR> tag (ambayo mimi figured nje na kuangalia chanzo na hazieleweki ni) na kisha kuchukua nafasi ya kwamba tag TR na ujumbe wangu. Mimi kwa kweli hawajui jinsi hii ni imara (Mimi nina mashaka sana, kwa kweli), but it worked in my sandbox. If I find a better way, Mimi itabidi blog juu yake. Hii ni matokeo:

image

Mimi bonyeza kifungo OK na data ni kubadilishwa na ujumbe kubwa nyekundu:

image

Kama unaweza kuwaambia, the way I’ve implement this “security” solution is to allow the web part to render itself. After it finishes, Mimi overwrite maudhui yake kwa mtazamo wangu "Hapana kwa wewe!"Ujumbe.

Pamoja na ukweli kwamba siyo kweli "kuulinda '" mtazamo, ni muhimu na uwezekano wa baadhi ya kazi na wajanja, it may eventually be securable in a more formal sense. The fundamental issue is that the client is getting all the data and then, tu baada ya anapata data, it wipes it out. If the client is getting the data, mtumiaji wajanja wanaweza kuzuia jQuery kutoka mbio wakati wote na kuona nini yeye / yeye anataka kuona.

There are other drawbacks. This “security” approach is based off a _spUserId. We’d want to really secure based on the full SharePoint security model, or at least by user name. That becomes progressively harder, lakini mimi kuona baadhi ya mambo mema imeandikwa juu ya somo hili, hivyo mimi nina matumaini kuna jibu nzuri na tatizo kwamba.

orodha ya maoni wenyewe lazima yachujwe, kama inawezekana. I haven’t tried to figure that out. I assume it’s possible, lakini si kweli kutatua kimsingi suala la usalama kwa sababu mtu bado anaweza tu aina URL ya maoni wanataka (kama walijua ni). Hata hivyo, trimming makes sense. It’s a good usability feature and it helps to obfuscate things. If an end user doesn’t know that the view event exists, they probably won’t try to use it. Wakati mwingine, kwamba nzuri ya kutosha.

Kwa bahati, Mimi itabidi zaidi ya kuandika juu ya mada hii baada ya muda.

</mwisho>

Kujiunga na blog yangu.

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

Haraka na Easy: Njia Bora ya kutumia jQuery kwa Ficha Shamba Nakala ya kidato SharePoint

Hii ni baada ya mwingine katika wangu inayoendelea mfululizo ya jinsi ya kutumia jQuery na SharePoint.
Kama unataka kujifunza zaidi kuhusu jQuery, Mimi sana kupendekeza: jQuery katika Action na kubeba Bibeault na Yehuda Katz.

Hapo awali, I wrote about how to use jQuery to locate and hide a text field on a form. I didn’t care for the specific approach (Nilikuwa chaining wazazi - kwamba tu si kufanyika siku hizi, angalau katika familia ya ubora).

Wakati mimi kwanza kuanza kufikiri juu yake, Nilijua zinahitajika ili kupata <TR> ambayo mimi naweza kujificha waomba() njia. My early effort to find the correct <TR> ilikuwa kitu kama hii:

$('Tr:ina(pembejeo[title = Ficha Me!])');

tatizo na kwamba ni kwamba itakuwa kupata kila <TR> tag that had any parent relationship to the Hide Me! shamba, hata kama Ficha Me! ni Furushi ngazi nyingi kirefu katika <TR>’s. It turns out that on my sandbox form, kujieleza kwamba hupata 9 tofauti ya TR ambao Ficha Me! as a child somewhere in its DOM tree. I realized that I could walk back up the tree from the input field itself, hivyo kwamba ni jinsi gani mimi kuishia wazazi kutumia vibaya, lakini hawakuwa kukaa vizuri na mimi.

Mimi alitoa mawazo ya baadhi ya hii na moja ya mambo ya mimi kusoma hatimaye alifanya akili: Mimi naweza kutumia si() njia ya trim nje <TR>’s I don’t want in my wrapped set. Kwamba aliniongoza hii:

$('Tr:ina(pembejeo[title = Ficha Me!])').si('Tr:ina(tr)').kujificha();

kwanza kidogo anaona kila <TR> vitambulisho ambayo Ficha Me! field anywhere in their own hierarchy. It then strips out any <TR> kwamba pia mtoto <TR>. This leaves us with a single <TR> kwamba:

1) Hana <TR> mtoto kumbukumbu

2) Does have the input field as child.

Tunaweza kisha kuomba kujificha() njia ya kuweka kusababisha na sisi ni kosa.

Mimi bado kidogo neva kuhusu hili, lakini si kama neva kama wazazi chaining.

I don’t know if this is a best practice or not. There may be a more appropriate way of identifying just the <TR> that we care about in a SharePoint form. If you know, tafadhali post comment.

</mwisho>

Kujiunga na blog yangu.

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

Haraka na Easy: Kutumia jQuery kwa Ficha Shamba Nakala ya kidato SharePoint

Hii ni baada ya mwingine katika wangu inayoendelea mfululizo ya jinsi ya kutumia jQuery na SharePoint.
Kama unataka kujifunza zaidi kuhusu jQuery, Mimi sana kupendekeza: jQuery katika Action na kubeba Bibeault na Yehuda Katz.

UPDATE (tayari!): Sikuweza kufikiri ya njia bora ya Machapisho <TR> tag nataka kujificha na aliandika juu yake hapa. You may still find this article interesting anyway so I’m leavnig it up.

Nataka kuficha Nakala shambani, "Ficha Me!"Kama inavyoonekana:

image'

jQuery zifuatazo hana hila kwa ajili yangu:

<script aina ="text/javascript">

  $(kazi() {


    $('Pembejeo[title = Ficha Me!]').mzazi().mzazi().mzazi().kujificha();

  });

</script>

kanuni ni kusema, "Kupata mimi mashamba yote pembejeo ambao title = Ficha Me!. Kisha, kupata mzazi wake na kisha mzazi ijayo na * ijayo * mzazi (phew!) na waomba kujificha() njia juu ya jambo, chochote ni hutokea kwa kuwa.

I figured nje kwamba muundo mzazi na kuangalia HTML kwa fomu kuwa SharePoint umba kama inavyoonekana:

<TR>
    <TD nowrap="true" valign="top" upana="190px" darasani="ms-formlabel">
        <H3 darasani="ms-standardheader">
            <nobr>Kujificha Me!</nobr>
        </H3>
    </TD>

    <TD valign="top" darasani="ms-formbody" upana="400px">
        <!-- FieldName="Hide Me!"
                 FieldInternalName="Hide_x0020_Me_x0021_"
                 FieldType="SPFieldText"
        -->
        <span wewe="none">
            <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="Hide Me!"
                darasani="ms-long" />
                <br>
        </span>


    </TD>
</TR>

Hii picha inaonyesha huo, lakini alama juu na wazazi:

image

mzazi wa kwanza (1) is a span tag. Span’s parent (2) ni tag TD na kisha hatimaye sisi kupata mzazi halisi nataka kujificha (3) ambayo ni tag TR yenyewe.

This is a pretty terrible approach I think because it’s extremely dependent on the very specific structure of this form. When SharePoint 2010 hutoka nje, this whole structure could change and break this approach. What I really want to do is craft a jQuery selector that is along the lines of “find me all the TR’s (na tu TR vitambulisho) kwamba kuwa mahali fulani katika watoto wao mambo ya shamba pembejeo ambao title = Ficha Me!". I starting from the bottom and moving up. Assuming I figure this out, Mimi itabidi baada updated "haraka na rahisi 'baada ya.

</mwisho>

Kujiunga na blog yangu.

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

Haraka na Easy: Kujenga jQuery yako mwenyewe Sandbox kwa SharePoint

Hii ni baada ya mwingine katika wangu inayoendelea mfululizo ya jinsi ya kutumia jQuery na SharePoint.
Kama unataka kujifunza zaidi kuhusu jQuery, Mimi sana kupendekeza: jQuery katika Action na kubeba Bibeault na Yehuda Katz.

Kupata ilianza na jQuery katika SharePoint ni ya kushangaza rahisi (kwangu). (I do have serious questions about a “best practices” approach to deploying these things to production, but that’s for another day). I’ve just started playing with this technology and to that end, I created a sandbox environment to use. If you’re looking to get started with jQuery, you may find this approach useful.

1. Create a Blank Site

Create a blank site somewhere in your site and call it something clever like “jQuery Sandbox”.

2. Download jQuery

You can download the jQuery javascript library from here: http://docs.jquery.com/Downloading_jQuery

Save that to to your desktop.

I have been using the “minified” version.

3. Create a SharePoint Document Library

In your sandbox site, create a document library.

4. Upload the jQuery Library to SharePoint

Access the doc library you just created and upload the jQuery library.

5. Create a Custom SharePoint List

I’ve started with a custom list because I want to muck about with standard SharePoint forms. You could also create a page in a pages library or web part pages and probably a lot of other places.

Add some columns to the custom list so that you have something to run jQuery against. My initial objectives were to:

  1. Hide a field.
  2. Assign a value to a field.

With that objective in mind, I added two text fields. Over time, I’ll be playing with links, images, lookups, nk.

6. Modify the NewForm.aspx Web Part Page and Add a Content Editor Web Part

This is a little black magic-ish , in that it’s a new concept to me. I first learned about this from Paulo Grenier, SharePoint jQuery Superstar, saa CodePlex yake tovuti ya mradi: http://spff.codeplex.com/.

Fuata hatua hizi ili kuongeza CEWP kwa ukurasa huo huo kwamba inaonyesha NewForm.aspx kwa orodha yoyote desturi:

  1. Kupata orodha ya desturi na bonyeza Mpya.
  2. Append zifuatazo URL: PageView = Shared&ToolPaneView = 2

Ambayo kubadilisha data yako boring vanilla kuingia fomu kutoka kwa kitu kama hiki:

image

Kwa hili:

image

Kuongeza mhariri maudhui ya mtandao sehemu ya ukurasa.

7. Kuandika jQuery wako kwanza Kanuni

Kufungua kwamba CEWP katika mtazamo wa kanuni na kuongeza yafuatayo:

image

Hapa ni kanuni halisi kama unataka nakala / kuweka:

<script
    "text/javascript"
    src ="../../jQuery Library/jquery-1.3.2.min.js">
</script>

<script aina ="text/javascript">
  $(kazi() {

    $('# ResultsID').html('Kuna' + $('A').ukubwa() + 'Vitambulisho vitambulisho kwenye ukurasa huu.');

  });
</script>

Kusababisha:
<div id ='ResultsID'></div>
/kusababisha

Note that the first <script> tag is referencing the actual jQuery library. Presumably, these things change over time, so you’ll want to make sure you a) use the right name and b) point it to the correct SharePoint document library.

Bask in the Glory

If you did it correctly, you’ll see a result similar to the following:

image

Wrapping Up

This isn’t the only way to get started, but it’s quick, easy and isolated from your existing SharePoint environment.

</mwisho>

Kujiunga na blog yangu.

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