UPDATE: 04/25/08: Zen harrapatzeko blog mezu batzuk eta artikulu honen lotura bat aurkitu: http://www.networkworld.com/news/2008/032608-microsoft-sharepoint.html?page=1. I make note of it because in addition to asking, "how do I learn sharepoint?", some people ask "why should I learn sharepoint?". That article partly answers the later.

Hainbat azken hilabeteetan, dozena bat edo gehiago planeta osoko Folks dira me badiozu mezu, eta, oro har, galdera eskatu, "How do I learn SharePoint?"

Autoritario ia ez naiz, baina izan dut arrakasta batzuk (eta hobeak lortzeko denbora guztian saiatzen) so I thought I’d document my personal road map. Others may find it valuable.

Ez dut horren aurretik, Nahi dut hori, niri bistako behatzeko, emailak horiek pertsonalak eta MSDN kopurua handiagoa oinarritutako / SharePoint Unibertsitatearen izaera bera mezu, that there is huge developer interest in getting up to speed with WSS/MOSS. I wonder what it’s going to be like a year from now … errazagoa ona SharePoint talentua aurkitzeko? The same? Are folks committing themselves to the platform at a rate sufficient to keep up with demand for good resources? How could you even figure something like that out short of a WAG?

Paul-en ibilbide-orria

I was full time employed by the good folk at Conchango while I followed this road map. This means that from a learning perspective, I was actively engaged in projects as I followed the steps I outline below.

Oinarrizko baldintzak batzuk

Mundu honetan sartzeko, bi gako akronimoak:

• WSS: Windows SharePoint Services
• Moss: Microsoft Office SharePoint Server

WSS is "free" hori da Windows zerbitzari batera saltzen 2003 (edo, gutxienez, MS deskargatu daiteke). I put quotes around free because you need a box, baliozko O / S lizentzia eta ziurrenik SQL (though there’s a "free" SQL mota baita).

MOSS is built on top of WSS and extends it. There is no MOSS without WSS. MOSS is not free.

Beharbada, ez da egun bat, baina laster duzun got ondoren plataformaren oinarrizko ezagutza batzuk, it’s important to learn the differences. Adibidez, indartsua web parte, Eduki Query Web Taldea, is a MOSS feature and not available WSS. People often make the incorrect assumption that CQWP is available in WSS and then end up scrambling for a stop-gap measure when they realize their error.

Asmatu Liburuak

I started working with WSS/MOSS on about 01/02/2007. I had a little prior experience with SPS 2003 but very little. To get myself started, Erosi dut bi liburu hemen agertzen (http://paulgalvin.spaces.live.com/lists/cns!1CC1EDB3DAA9B8AA!203/).

I started with the big blue administration book. Naturally, it covers administration. Aldi berean,, MOSS ezaugarri guztiak inkesta bat ematen du, (WSS eta ezaugarriak, bai).

Niretzat, ez da hain garrantzitsua, hainbat xehetasun guztiak gogoratzeko (bere denbora ziurtatuta lortu arte) but it’s good to know the boundaries. (Berean planteamendu hau jarraitu dut 1go pertsonan shooters play Xbox edo PC dut — I enter a room and tend to make a counter-clockwise loop until I get back where I started. I just feel better knowing the shape of the box I’m in.)

Big blue liburua irakurri ondoren, I would read the entire Inside WSS book. It dives deeply into issues that developers care most about.

Sortu birtuala Ingurumena bat

Ordena garapen edozein egiteko edo ingurune egokian erabili, osoa pizten leihoak zerbitzari eragile SharePoint Designer-sistema behar duzu, Visual Studio 2005 (2008 lan egiten du, baina tresna batzuk izan gabe, artikulu honen idazketa aurrera eraman ahal izateko), InfoPath 2007 and some other stuff. There are many good blog entries describing this process. I’d have a look at these two:

• Nola MOSS bat eratu 2007 VPC irudia: Osoan 9 Metro – SharePoint Reporter Bloga
• Nola SharePoint Garapenerako sustatzailearen optimoa VPC eraikitzeko – Bloga

Horrez gain, Andrew Connell partekatu bere esperientziak VMWare hemen:

• Microsoft-en birtualizazio produktuak vs. VMWare en eskaintza

Use your favorite search engine to see what other people do. It’s a useful learning exercise in and of itself.

Spend a few minutes angrily denouncing the fact that you need a server environment on which to do development. Baina … don’t bother blogging about it or posting it to MSDN forums. It’s already been done 🙂. Horren ordez, embrace it and move on. You’ll be better off for it.

Parte Certified

Dut uste MS SharePoint ziurtagiri-bide, osatzen dute, horietatik lau azterketak, is exhaustive. I suggest that you follow their online preparation guide and do your best to understand each of the areas of the test.

I ez suggest that you take the exam just to pass it. I ez suggest that you use one of the "brain dump" style 3rd party "tools" for passing MS tests. If you can take the test, pasatzen da zure oinarritzen zuzendu egin ikasketa-konbinazio batean eta esperientzia eskuak-on, sendoagoa sustatzailearen eta lan hori egiteko hautagai izango zara.

There are four tests in two "tracks":

Garatzaile:

• TS: Microsoft Windows SharePoint Services 3.0 – Aplikazioen garapena
• TS: Microsoft Office SharePoint Server 2007 - Aplikazioen garapena

Admin:

• TS: Windows SharePoint Services 3.0, Konfiguratzea
• TS: Microsoft Office SharePoint Server 2007, Konfiguratzea

I recommend that developers study for all of these exams. You’ll be strong for them, Suposatzen dut Saltatutako baduzu admin azterketak nahiz, lortuko lituzke arabera.

WSS bertsio aurkitu dut nabarmen gehiago MOSS dagokion bertsio baino erronka izango da, much to my surprise. I was in a class recently and several others made the same point.

Zen nintzen bitartean ikasten 70-542 azterketa- (MOSS garapena) I tracked my study resources. These may be helpful to you as well: http://paulgalvin.spaces.live.com/Blog/cns!1CC1EDB3DAA9B8AA!192.entry

Plug Yourself Erkidegoko Into

SharePoint komunitate dardarkaria, sendo eta handiagoa hazten ari den denbora guztian.

Honako begiratu hasteko nahi duzu:

• Blogs
• Foroak
• Codeplex
• Twitter

Blogs

Ez baduzu ulertzen RSS, stop everything and learn it. It will take 10 minutuan ikasteko, agian beste 10 minutuan oinarritzen RSS reader web bat aurkitzea (Google-en irakurlea gogoko dut, www.google.com / reader).

Start by adding this blog to your RSS reader 🙂

Hurrengoa, gehitu www.sharepointblogs.com to your reader. They aggregate many blogs into a single feed.

Denborarekin, you’ll find blogs that are not aggregated that way. Just add them individually.

I subscribe to a few dozen blogs which I’ve accumulate over the last year. Nahi baduzu, Nire zerrenda esportatu ahal izango dut, eta mezu elektroniko.

Azkenean, you may want to start your own blog. I personally think that a series of blog entries describing a "newbie’s" aurrerapen WSS / MOSS ikasteko interesgarria serie bat izango litzateke. Egin nuen neure burua, nahi duten.

Foroak

Foro bi taldetan aktiboki parte hartzen dut: MSDN eta SharePoint Unibertsitatea.

Forums are excellent places to learn. People ask questions ranging from the very simple ("How do I create a site column") panicked nahi du ("My server is down!") gehiago hipotetiko diseinua galderak.

Behin ingurumena zapore bat lortuko duzu, venture out and start replying. Short of directly interacting with a customer, ezer ez da hau baino hobea esperientzia eskuak.

Codeplex

Hona joan www.codeplex.com.

Begira eta SharePoint-proiektuak bilatzeko.

Eguneroko laburpena Codeplex feed izena eman zure feed irakurle.

Gehitu edozein proiektu berriak SharePoint zure jario irakurleari.

Azkenean, foroak irakurtzeko eta behera zeure WSS / MOSS deabru aurre egin ondoren, iritziz, elkarrekin jarriz zeure codeplex proiektua.

Twitter

Idazten dut blog sarrera hau, SharePoint folk asko hasi ziren erabiltzen Twitter.

It’s hard to characterize Twitter. You’ll just have to check it out yourself.

Ondorioa

That wraps up my roadmap and makes me current. I just started using Twitter two weeks ago.

WSS/MOSS is a very cool platform and the community is growing all the time. Use community resources to improve your skills and enjoy the journey!

</amaiera>

Nire blog Harpidetu.

UPDATE: An anonymous person in the comments posts this link: http://www.atidan.com/atidan-collaboration-kit.php

Foroa erabiltzaile sarritan galdetu horrelako galdera bat:

"I would like to have a calendar at the site level that is populated by events from subsite calendars. Ideally, subsites erabiltzaileen egutegi-gertaerak sortzen ditu,, and will have the option of marking them as ‘public.’ Events marked as public will dynamically appear in the shared site calendar. Thus the shared site calendar is a roll-up of all public events from all subsite calendars."

Da WSS 3.0 edo MOSS 2007, it is not possible to directly configure a "roll-up" calendar. Calendars exist on their own, beste edozein egutegi independentea.

Roll-up egutegi bat sortzeko, jarraitu bide horietako bat:

1. Use a Content Query Web Part. This is the easiest solution for MOSS users (WSS ematen ez CQWP). CQWP, zoritxarrez, does not provide a calendar view of data out of the box. It does provide enormous rendering flexibility (Hemen adibide bat egiteko) baina lehenetsi, shows its results in simple list format. In many cases, CQWP seguruenik aukera ona.
2. A more programming-oriented solution would be to use event receivers. Implement event receivers on the subsite calendars that keep their public events in sync with the master calendar. As a given subsite calendar is modified, reach out to the master calendar and update it as needed. This option is available in both WSS 3.0 eta MOSS.

There are probably other clever solutions to this problem. If you have one or know of one, Mesedez, utzi iruzkin bat, edo email me eta post hau eguneratu egingo dut.

</amaiera>

Nire blog Harpidetu.

Dezakegu, behar du, eta, hainbat aldiz sor ez SharePoint zerrendetan (Dokumentu liburutegiak, Ohiko zerrendak, etc). SharePoint always lists available views in alphabetical order. We cannot change this using out of the box functionality. If it can be done via customization (eta ez nago ziur aski), urrun da tekniko zure amaiera tipikoa erabiltzaile.

Nahi duzu diren ordena SharePoint zerrendatzen eskuragarri aldiz kontrolatu nahi baduzu, besterik gabe, gunearen aurretik zenbaki bat edo gutun ikuspegi izena, bezala:

1 – Material motaren arabera
2 – Dokumentu guztiak
3 – Epemuga

-edo-

A – Material motaren arabera
B – Dokumentu guztiak
C – Epemuga

I have also created views whose purpose is strictly to feed a KPI. I have been following this naming convention:

Z_KPI_[deskribapena]

That causes my "KPI" aldiz zerrendaren behealdean agertzen.

</amaiera>

Nire blog Harpidetu.

Gaur egun, I was working with a client and describing how to modify the content query web part and display additional bits of information from a content type.

"First, CQWP du bere datu-iturri konektatu konfiguratu, ondoren, esportatu zure lanpostua, aldatu <CommonViewFields>, igo, remove the original and now it’s ‘primed’ to display those other columns. Hurrengoa, ireki SharePoint diseinatzailearen, navigate to the site collection root and locate ItemStyle.xsl. Copy one of the templates as a useful starting point. Go back and modify the CQWP to make use of this new template. Azkenik, aldatzeko plantilla zure eremu berriak eskaintzea! (Ez ahaztu egiaztatu berriro, beraz, beste erabiltzaileek emaitzak ikusi ahal)."

Dena nahiko argi me (eta gurekin gehienak SharePoint sustatzailearen motak) zer gertatzen den eta nola nahiko polita da, benetan, that the data retrieval aspects of the CQWP are so well-separate from the data presentation aspects. Baina, ez da hain erraza, azaldu, da?

<amaieran />

To filter for a query for the Yes/No check box entitled "PG Milestone", konfiguratzeko hau atsegin CQWP:

Beraz, begi-bistakoa-behin-you-jakin-baina hard-to-find-bat-erantzun-galdera beste bat da: Nola Bai / eduki kontsulta web parte-laukia erabiliz No iragazi.

Lehen bilaketa-emaitza I find using the search term "filter yes/no content query web part" laua da gaizki atera, beraz, hau jarri nuen han ikusi eta okerrak emaitza ordeztu bada dezakezu bilaketa tipikoa emaitzak pentsatu nuen.

Nahiko erraza da: True values = "1" and false values do not equal "1" (nahiko retro, benetan).

Goiko adibidean, I created site column of type "Yes/No (kontrol-laukia)" named "PG Milestone". I added it to a doc library, Igotako gutxi dokumentu bat, ezarri pare bat balio du, eta probatu.

<amaieran />

UPDATE 12/04/07: Ikusi this Microsoft KB (http://support.microsoft.com/kb/923589) Informazio lotutako.

Benetan, bihurtzen da da, baina tricksy MOSS had to make it difficult.

My customer does some development work on his MOSS site over the weekend. It’s a bit of a jumble as to what he actually did, baina azken emaitza hau da::

• He tries to add a site column called "Quantity" and MOSS replies: "The column name that you entered is already in use or reserved. Choose another name."
• He attempts to add it to another environment and that works. Hori dela eta, "Quantity" is not a reserved name.
• He tries to find an existing site column named "Quantity" in that site collection. He cannot find it.

I did some research, and even some coding, waxed philosophical and finally found that a column named Quantity did, Izan ere,, exist. It was in the "_Hidden" group. Hence, we could not find it via the SharePoint user interface.

How did it get there? I do not know, but I have a theory (or as my wife would call it, "blah blah blah"). Nonbait, lerro zehar, bat fabulous forty template was added and probably activated at a site in the site collection. It was then deactivated (or the site removed). The site column, Hala ere,, remained but in the "_Hidden" group. If someone knows better, please let me know via e-posta or post in the comments.

SharePoint was telling the truth. It’s hardly worth pointing out that that message is not as helpful as it could be. It would be nice to see that message fork into two different messages in the future: 1) Say that the column name is reserved or it is not. 2) If it’s not reserved, show the site, or at least the group, where the column name is already used.

</amaiera>

Aste honetan, erreproduzitu, azkenik dugu arazo bat izan da urruneko erabiltzaile berri: Zerrenda edukiak esportatzeko excel saiatu zuen, gauzak lanean hasteko badirudi, baina gero, Excel irekiko luke errore bat: "Cannot get the list schema column property from the SharePoint list". She was running office 2003, windows XP and connecting to MOSS.

Internets bilatu dut eta espekulazio batzuk, baina ez du ezer ikusi 100% definitive. Hence, post honetan.

Arazoa: Ikuspegi esportatu Excel duten data bat dauka (data = zutabean datu mota).

Zer Gurekin lan egin: Convert the date to a "single line of text". Gero, bihurtzeko bueltan data.

That solved it. It was nice to see that the conversion worked, benetan. It was quite nervous that converting things this way would fail, but it did not.

Bug hau bota itzal handi bat, datu-mota baino gehiago bezeroaren kontuan, beraz, bila itzazu Microsoft, behin betiko erantzun bat dugu, eta ea argitaratzeko eta eguneratzeko dut hemen hurrengo denbora epe labur euren erantzun ofiziala eta informazio Hotfix zuzenketa batera.

Beste erreferentziak:

http://www.kevincornwell.com/blog/index.php/cannot-get-the-list-schema-column-property-from-the-sharepoint-list/

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2383611&SiteID=1

<amaiera>

Nire blog Harpidetu.

Azken bi egunetan zehar, I have participated in two meetings during which we presented the results of a SharePoint project. The CIO and his team joined the first meeting. That’s standard and not especially notable. The IT department is obviously involved in an enterprise rollout of any technology project. The second meeting expanded to include a V.P. marketing-tik, hainbat ordezkari, zuzendari HR, Logistika, Fabrikazio, Capital Proiektuak, Kalitatea, Erosteko, Korporatiboaren garapena eta beste sail (eta horietako batzuk ez ziren zuzenean, egungo fasean parte hartzen). That’s a mighty wide audience.

Nire bizitza, aurreko, I primarily worked on ERP and CRM projects. They both have a fairly wide solution domain but not as wide as SharePoint. To be fully realized, SharePoint projects legitimately and necessarily reach into every nook and cranny of an organization. How many other enterprise solutions have that kind of reach? Not many.

SharePoint clearly represents an enormous opportunity for those of us fortunate enough to be in this space. It provides a great technical opportunity (hau da, nolabait esateko, bere burua aktibatuta hemen under "Technologies You Must Master"). But even better, SharePoint exposes us to an extensive and wide range of business processes through these engagements. How many CRM specialists work with the manufacturing side of the company? How many ERP consultants work with human resources on talent acquisition? SharePoint exceeds them both.

Atsegin dut ezer, ez da perfektua, baina madarikatuak leku ona izan da.

Buruzko SharePoint foroak, someone occasionally asks about "changing the label of Title" or about "removing title from lists".

Behean line: Baina ez du!

Tamalez, Erabiltzaile interfazea zutabea duten aldaketa bat-modu bat agerian uzten du:

Title is a column associated with the "Item" eduki mota. Asko, asko, CT horrek asko erabili zutabe hau eta aldatu baduzu hemen, it ripples out everywhere. There’s a good chance that you didn’t intend for that to happen. You were probably thinking to yourself, "I have a custom lookup list and ‘Title’ besterik ez du zentzurik zutabean izen bat, so I’m going to change it to ‘Status Code’ and add a description column." But if you follow through on that thought and rename ‘Title’ to ‘Status Code’, zerrenda behin izenburua (Dokumentu liburutegiak barne) changes to "Status Code" eta ziurrenik ez zuen asmoa hori dela-eta.

Benetako arazoa da hori, bat-modu bat da aldaketa. The UI "knows" that "title" is a reserved word. Beraz,, if you try and change "Status Code" back to "Title", saihesteko duzu izango da eta orain dituzun zeuk margotu izkinan using paint that never dries 🙂

Beraz, zer gertatzen da dagoeneko aldatu bada? I haven’t seen the answer we all want, which is a simple and easy method to change the label back to ‘Title’. Right now, the best advice is to change it to something like "Doc/Item Title". That’s a generic enough label that may not be too jarring for your users.

Gutxi beste ideia nire egiteko gauzen zerrenda ikerketa dira daukat:

• Harremanetan Microsoft.
• Zerbait objektu ereduaren, agian ezaugarri bat batera.
• Irudikatu datu-basearen eskema eta eskuz SQL eguneratu. (Microsoft harremanetan jarri beharko duzu hori egiteko, nahiz eta aurretik; ziur aski gal zure laguntza-kontratua).

Edozeinek daki nola konpondu nahi bada, mesedez, post a comment.

Eguneratu arratsean, 11/15: Lotura hori metodo bat deskribatzen zerrenda-mota bat sortzeko ez duten titulu zutabe bat aurkitu dut: http://www.venkat.org/index.php/2007/09/03/how-to-remove-title-column-from-a-custom-list/

Aste bat inguru ago, I started up a codeplex project that provides a simple and reasonably generic method for adding custom action functions to SharePoit Designer workflow. It’s described here: http://www.codeplex.com/spdwfextensions. Beyond simply providing a framework, it also aims to provide a set of useful functions that will make SPD more useful/flexible/powerful.

Hemen bertsioaren planifikatutako egungo ezaugarriak 1.0: https://www.codeplex.com/Release/ProjectReleases.aspx?ProjectName=spdwfextensions&ReleaseId=8280

Edozeinek proiektu honetan inolako interesik badu, Mesedez, utzi iruzkin bat, edo / eztabaida bat gehitu hemen: http://www.codeplex.com/spdwfextensions/Thread/List.aspx

Hemen funtzio dituzte kodetuta multzoa uneko (ez da erabat bezain probatu 11/08/07):

Funtzioa	Deskribapena (berean ez bada ere. funtzio garbia)
Num-sarrerak()	Returns the number "entries" in a string as per a specified delimiter. Adibidez: Num-entries in a string "a,b,c" with delimiter "," = 3.
Sarrera()	Returns the nth token in a string as per a specified delimiter.
Luzera	String.Length
Ordeztu()	String.Replace()
Dauka()	String.Contains() Returns the word "true" or the word "false".
Izan ezik:(hasteko)	String.Substring(hasteko)
Izan ezik:(hasteko,amaiera)	String.Substring(hasteko,amaiera)
ToUpper()	String.ToUpper()
ToLower()	String.ToLower()
StartsWith()	String.StartsWith() Returns the word "true" or the word "false".
EndsWith()	String.EndsWith() Returns the word "true" or the word "false".