Azkarra eta erraza: Erabili jQuery A Testu Eremuaren en balioa ezartzean SharePoint formularioa batean

5 Erantzunak

Inguruan jolasean hasi nintzen jQuery yesterday. I’ve been wanting to do this for a long time, geroztik Paul Grenier hasi idatziz bere serie Azken erabiltzaileentzako jQuery agurgarri buruzko 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.

Egoera honetan, Sortu dut zerrenda pertsonalizatu honen "berri" forma itxura gisa agertzen:

image

Hau zerrenda pertsonalizatu formularioa lehenetsia Izenburua zutabe eta bi zerrenda zutabe berria da (Ez gune zutabeak; Ez dut uste diferentzia bat egin beharko du,).

Helburua da eremua balioa arbitrarioa bat esleitzeko, "DefaultMeFieldNoSpaces" (esango koldar bat pixka bat naiz "hutsunerik gabe" gauza on going dezakezu, baina espezie gora egin dut, artikulu honen amaieran).

JQuery apur hau niretzat lan egin:

<script mota ="text/javascript">

  $(funtzioa() {

    $('Sarrera[title = DefaultMeFieldNoSpaces]').Pantailazatiak(
        {balioa: 'Dira pasarte twisty labirinto bat duzu, guztiak berdin. '});

  });

</script>

Ulertzen dut gisa jQuery apur hori esaten, “find me any input tag whose title = DefaultMeFieldNoSpaces. Gero, beren balio guztiak bat ordenagailu zaharrak jokoa esaldi ospetsua da. "

Han soilik izango geroztik izango eremu bat formularioa izenburu bat "DefaultMeFieldNoSpaces" Parekatuak gara Eremu duten balioa esleitzeko ziurtaturik eta ez beste.

Eremu bat bere izena du espazio buruz zer? It’s nearly the same:

<script mota ="text/javascript">

  $(funtzioa() {
     $('Sarrera[title = Space eremua esleitu]').Pantailazatiak(
        {balioa: 'Dira pasarte twisty labirinto bat duzu, guztiak berdin. '});

  });

</script>

Hau nahiko seguru hurbilketa bat dela uste dut, 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, narratsa moduko da:

<sarrera
izena="ctl00$m$g_bdb23c2c_fde7_495f_8676_69714a308d8e$ctl00$ctl04$ctl02$ctl00$ctl00$ctl04$ctl00$ctl00$TextField"
mota="text"
maxlength="255"
id="ctl00_m_g_bdb23c2c_fde7_495f_8676_69714a308d8e_ctl00_ctl04_ctl02_ctl00_ctl00_ctl04_ctl00_ctl00_TextField"
izenburua="DefaultMeFieldNoSpaces"
klasean="ms-long"
/>

"Izenburua" nabarmentzen bat ezagutzeko eta espero berezia atributu gisa, berariazko zutabea, gure arbitrarioak balioa esleitu nahi dugu identifikatzen laguntzeko.

This is a foundational concept. Setting a field in an arbitrary way like this isn’t going to win any awards. Hala eta guztiz ere, nahi dugu gehiago interesgarri inprimaki maila zerbait egin nahi izanez gero, (horrek guztiok beti nahi, jakina, ondoren platerak bukatzen dugu garbiketa), gustatzen aldatu automatikoki "Eremu bat" balioa oinarritutako "eremuan b" balioa, dugu (I) behar gauza horiek ikasteko.

Gure onena aukera bat benetako balioa erabilgarria lortzeko hemen izenburuaren bidez egiten da, uste dut, at least for text fields. There may be a better, more reliable approach. If I find it, Post hau eguneratuko dut. If you know a better way, Mesedez, utzi iruzkin bat.</amaiera>

</amaiera>

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin

SharePoint manifestazioa: Leverage SharePoint, Business eskaera bertikala bat eraikitzeko

Utzi erantzun bat

[Kontuan izan: Berehalako esan manifestazio honen emaitza nahi duzun interes finantza que tengo nahi dut, aipatzen, dibulgazioa osoa interes I, etc. This is actually the first time I’ve ever blogged about an event where I stand to benefit personally in this way.]

Web manifestazio hau gertatzen osteguna, 06/04 at 12:30 EDT, amaitzen 1:30PM EDT.

Nire negozio bikaina bazkide elkarlanean, Integrated Systems eta Zerbitzuak Grupo (ISSG), I have been working to develop a vertical business application using SharePoint as the platform. Kasu honetan, 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, salmentak barne, ingeniaritza, ikerketa eta garapena, juridiko eta beste talde batzuk.

Demo aplikazio bat da, lankidetza-mota hori errazten erakusteko joan, nola lankidetza bit horiek guztiak behar bat ERP euskarri-sistema integratu buruzko eztabaida bat batera.

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

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

Oraindik Interesaturik bazaude, please sign up here(https://www323.livemeeting.com/lrs/8000043750/Registration.aspx?pageName=skmqfwbr5smmlx20).

</amaiera>

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin

SharePoint Designer Pry Ezin duzu My Cold., Dead Eskuak

Utzi erantzun bat

Nire azken artikulu at sortu da www.EndUserSharePoint.com. I wrote about SharePoint Designer, Amaiera erabiltzaileak eta azken erabiltzaileek eta saiatu liteke jarraitu ahal izateko gaitasuna erakusteko tresna honen inguruan eta konfiantza eraikitzeko estrategia baten eskema.

Iruzkinak article bera baino interesgarri gehiago.

Ezazu.

</amaiera>

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin

Eraginkortasunez Jarraitu Microsoft SharePoint (eta Beste) SharePoint Foroak

2 Erantzunak

Izan dut MSDN foroak jarraituz ondo urtebete baino gehiago (eta, seguru asko, ia 2 puntu honetan urte) 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).

Taking MSDN as an example, I first go to standard forum page such as the General Questions for SharePoint main page here: http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/threads

You should right away notice that the forums are RSS enabled, ikus daitekeen bezala:

image

I’ve been using Google Reader for managing my RSS feeds for a long time now (www.google.com / reader). 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 provides me a nice view of the posting itself:

image

Eta, azkenik,, Google ematen dizu teklatua erabil dit foroetan mezuak joateko modu honetan.

Azkar ezin dut mezu bidez eskaneatu eta soilik sentitzen naiz zentratu erabilgarria ekarpen bat egin ahal izango dut.

Alerts close the loop. Updates to posts don’t come through RSS (Nik uste dut, erabilitako denbora luze bat dute, nahiz eta duela). Hala eta guztiz ere, Zelan foro batean mezuak bidaltzeko erantzun bat bada, the forums alert me via email and IM that someone responded in turn. Edo, ezin dudanean egin erabilgarria ekarpen bat da, baina beste batzuk, zer esan jakin nahi dut, Sartu ahal izango dut zulatzeko eta alertak esplizituki eskatu denean, beste batzuk erantzuteko.

Ordubete edo gutxiago, prozesu hori ezar dezakezu, eta ohiko erabileran, eta aste batean, ikasteko, hainbat trikimailu eta teklatu lasterbideak da, beraz, bigarren izaera bihurtzen da.

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

Foroak awesome modu bat dira, ziurrenik modurik onena, zuzeneko esperientzia pertsonala laburrean, produktua ikasteko eta nola munduko inkesta polit bat lortzeko, handietako, uses SharePoint. Give it a try!

</amaiera>

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin

Technorati Tags:

Erabili pertsonalizatua zerrendak eraginkorragoa Workflow Ikuskaritza egiteko

2 Erantzunak

Berrantolatu dut nire bizitza pixka bat eta denbora bat aurkitu artikulu bat bidaltzeko www.endusersharepoint.com. My latest article is up here: Erabili pertsonalizatua zerrendak eraginkorragoa Workflow Ikuskaritza egiteko (http://www.endusersharepoint.com/?p=1658).

Honen inaugurazio 'grafikoa da:

SharePoint Designer workflow doesn’t give us a lot of visibility into what’s happening with our workflow solutions. Eta, ikuspena egin hori iritsi da nahiko pobrea interfazearen arabera eragotzi eta 60 day time window. Hau 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, sortu workflow konponbide "saioa historia zerrenda" baliatzen ekintza ...

Arazoa da, ondoren 60 egun, mezurik sortu beharko duzu, modu honetan daude historia workflow zerrendatik ezabatu! After a bit of teeth gnashing and “what were they thinking?"Argumentu, beheko lerroa hau: it happens and it needs to happen. Galdera da, Nola inguruan dugun?

The official answer is to rely upon SharePoint’s built-in auditing feature. From an end user’s point of view, Hala ere,, that’s very weak in WSS and not much better in MOSS. Zorionez, 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.

Ezazu.

</amaiera>

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin

Banbu Egutegia SharePoint elkarreragina sortzeko "ustekabeko errorea gertatu da"

1 Erantzun

Gaur egun, 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, bat "Aplikazio zerbitzaria" indexatzeko eta InfoPath eta taldekatuta SQL atzera amaierako.

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, besterik ez duen esaldia.

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, Bat-batean, Niri erakutsi du polit bat ordenatu errore mezua:

image

Ez dakit zer gertatzen ari zen, edo zer kontrolatu errore mezua iritsi erantsi baino beste erakutsi nuen ?contents=1 bit of the query string.

Hau da, ziurrenik oso arraroa ertzean kasuan, baina lortuko duzu mezu hori bada,, "Ustekabeko errorea gertatu da" aurrera eta gehitu ?edukia = 1 kontsulta katea ikusi eta non doan.

</amaiera>

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin

Technorati Tags: ,

Windows Live buruzko Griping Iruzkina Kontrol

2 Erantzunak

Windows Live Spaces jaso nuen uztailaren hasieran 2007 as my blogging platform. For the most part, Ez dut damurik eta Microsoft zalantzarik gabe zabaltzen da, denboran zehar (batez ere, nahiz eta aurkitu dut izarrekin ezaugarri berriei buruz istripuz).

My biggest complaint right now is blog spam. This person / Kontu (http://cid-82b0534bceed9881.profile.live.com/) (besteak beste,) 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 (aurretik, ordea,, Blog-sarrera bakoitza bereizita sartu nuen) and clean them up. It’s still time consuming.

Dut nahi:

  1. MSFT spam iragazketa hobeto batzuk jartzen.
  2. Berariazko pertsona blokeatu liteke iruzkinak gehituz tik.
  3. Aurrekoez ezean, I could more easily identify and delete spam. Right now, Duzu iruzkinak egin behar dut eta motela da,, batez ere zenbait spam robot pertsona / programa gehitzen 25 to 50 en saio iruzkinak.

Oraindik Windows Live erabiltzailea badago eta erabilgarria trikimailu batzuk partekatu, Eskertuko nuke.

</endGripe>

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin

SharePoint Larunbata Fenomenoa jarraitzen (plus, nire diapositiba bizkarreko)

Utzi erantzun bat

Washington DC itzuliko naiz atzo azken bertaratu ondoren SharePoint larunbata. What a remarkable event! Continuing the tradition of other SP Saturday’s, it was very well run. The environment, oro har, erakundearen, fluxua, saltzaileari gunea, janaria ... Hori guztia izan zen emanaldirik.

Jakina, onenek parte edukia da, eta ez dut uste inork zen etsita.

Benetan nahiko niretzat harrigarria da zenbat jende asko dira rousing beraiek ohetik goiz Larunbata bat, eta joan den jendea eztabaida entzun SharePoint about 8 hours 🙂 Amazing.

Odds dira, ez dago bat SharePoint Larunbata gertaera zure bidea datozen da eta ez badago, zergatik ez duzu bat hasteko?

Aurkeztutako hitzaldian dut bihurrituz hizkuntza izenburu, “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.

</amaiera>

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin

Gobernantza Marketing Plan bat da gehiegi

3 Erantzunak

Arrazoia, hainbeste denbora pasatzen dugun (edo behar, hala ere) 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.

Desiragarria helburu hori lortzeko, gobernantza dokumentu eta plan sorta bat "duc" devolve eta "ez duc-en", bezala:

  • Ez Thou SharePoint segurtasun taldea sortu; erabili AD ordez.
  • Ez Thou dokumentu liburutegietan karpetak sortu; eduki-motak eta aldiz erabili ordez.
  • Dokumentu guztiak eduki mota sortu ditu Thou oinarritutako oinarri pertsonalizatu espezifiko mota off.
  • Ez Thou gaur egungo enpresa org taula off oinarritutako taxonomia bat sortu.

"Gorte Orokorre Thou" eta "ez zara", zalantzarik gabe, bere lekua izan gobernantza 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. (Daude Fringe kasuetan ez da beharrezkoa komunitatearen lankidetza, adibidez SharePoint ongi kudeatzen erabiltzaile kopurua oso txikia da erabiltzen; Ziur besteen dezakezu uste dut). 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.

</amaiera>

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin

Irtenbidea: MOSS Audience konpilatzea New Members No gehitzen

Utzi erantzun bat

Behean line: erabili nahi duzun profila jabetza arau batean ikusleak sortzeko, jabetza ikusgai egon behar du "denek".

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. Kasu honetan, ikusle jabetza izeneko "SITECD" eta hitzarmena, gordetzen bat 3 pertsonaia kodea. Ikusleen eta arau bat esan badu, "SITECD berdinen 'ABG' definitu zuen", ondoren, besteak beste, erabiltzaile hori ikusleen profila.

Erabiltzaile bakar profila sortu zuen balio duten eta ikusleen konpilatu, but MOSS simply wouldn’t add that user. I noticed that the privacy setting for that profile was set to “me only” (inprimaki murriztaileak) 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 azaldu: Microsoft Office SharePoint Server Informazio Langileen sartu Dive Deep 2007, eta estaltzen dut puntu hau oso atalean idatzi dut :). I would have thought that every word I wrote in that chapter would be seared into my memory.

Matt Morse xehetasun ederra sortu hau idatzi hemen eta erreferentziatutako I kapitulua: http://blogs.pointbridge.com/Blogs/morse_matt/Pages/Post.aspx?_ID=50

</amaiera>Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin

Technorati Tags: ,