UPDATE: 04/25/08: Var smitandi upp á sumum bloggfærslum og fann link á þessa grein: 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.

Á síðustu mánuðum, tugi eða fleiri gott fólk frá yfir jörðinni hafa verið að senda mér póst og spyrja almenna spurningu, "How do I learn SharePoint?"

Ég er varla opinber, en ég hef haft nokkrum árangri (og reyna að fá betri allan tímann) so I thought I’d document my personal road map. Others may find it valuable.

Áður en ég gera það, Ég vil bara að sjá að það er augljóst að mér, byggt á þessum persónulegum tölvupósti og jafnvel fleiri MSDN / SharePoint Háskólinn innlegg af því tagi, 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 … auðveldara að finna góða SharePoint hæfileika? 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?

Páls Roadmap

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.

Sum Basic Terms

Fyrir fólk að slá þessum heimi, Það eru tveir helstu skammstafanir:

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

WSS is "free" í að það er búnt með Windows Server 2003 (eða að minnsta kosti er hægt að hlaða niður frá MS). I put quotes around free because you need a box, gild O / S leyfi og sennilega SQL (though there’s a "free" konar SQL og).

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

Kannski ekki dag einn, en fljótlega eftir að þú hefur got sumir undirstöðu þekkingu á vettvang, it’s important to learn the differences. Til dæmis, öflugur vefur hluti, Fyrirspurnin Content Web Part, 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.

Hit bækurnar

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, Ég keypti tvær bækur hér (http://paulgalvin.spaces.live.com/lists/cns!1CC1EDB3DAA9B8AA!203/).

I started with the big blue administration book. Naturally, it covers administration. Á sama tíma, það veitir yfirlit yfir öll mosa lögun (og WSS lögun eins og heilbrigður).

Fyrir mig, það er ekki svo mikilvægt að muna eftir öllum þeim ýmsar upplýsingar (þar kominn tími til að fá staðfest) but it’s good to know the boundaries. (Ég fylgja þessum sömu nálgun í 1. persónu Fram ég spila á Xbox eða PC — 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.)

Eftir lestur stóru bláu bókina, I would read the entire Inside WSS book. It dives deeply into issues that developers care most about.

Búa til raunverulegur umhverfi

Til að gera allir þróun eða almennilega að nota umhverfið, þú þarft a fullur uppgefinn Windows Server stýrikerfi með SharePoint Designer, Visual Studio 2005 (2008 virkar, en nokkrar gagnlegar verkfæri hafa enn verið flutt frá og skrifa þessa grein), InfoPath 2007 and some other stuff. There are many good blog entries describing this process. I’d have a look at these two:

• Hvernig til Skapa a mosa 2007 VPC Image: The Whole 9 Metrar – SharePoint Fréttaritari Blog
• Hvernig á að byggja hagkvæmustu verktaki VPC fyrir SharePoint Development – Blog

Auk þess, Andrew Connell deildi reynslu sinni með VMWare hér:

• Microsoft virtualization vara Vs. Gjafir VMware

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. En … don’t bother blogging about it or posting it to MSDN forums. It’s already been done 🙂. Staðinn, embrace it and move on. You’ll be better off for it.

Fá staðfest

Ég tel að MS SharePoint vottun Path, sem samanstendur fjórum prófum, is exhaustive. I suggest that you follow their online preparation guide and do your best to understand each of the areas of the test.

Ég ekki suggest that you take the exam just to pass it. Ég ekki suggest that you use one of the "brain dump" style 3rd party "tools" for passing MS tests. If you can take the test, gefa það byggist á samblandi af eigin beint rannsókn og snertið ekki-á reynsla, þú munt vera sterkari verktaki og starf frambjóðandi fyrir það.

There are four tests in two "tracks":

Verktaki:

• TS: Microsoft Windows SharePoint Services 3.0 – Umsókn Þróun
• TS: Microsoft Office SharePoint Server 2007 - Umsókn um þróun

Admin:

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

I recommend that developers study for all of these exams. You’ll be strong for them, þó að ég geri ráð fyrir ef þú sleppt því að admin prófum, þú vildi fá með.

Ég fann WSS útgáfa að vera töluvert meira krefjandi en samsvarandi útgáfur mosa, much to my surprise. I was in a class recently and several others made the same point.

Meðan ég var í námi fyrir 70-542 próf (MOSS þróun) I tracked my study resources. These may be helpful to you as well: http://paulgalvin.spaces.live.com/Blog/cns!1CC1EDB3DAA9B8AA!192.entry

Tengdu þig í bandalaginu

The SharePoint samfélag er lifandi, sterk og vaxandi stærri allan tímann.

Þú vilt líta á eftirfarandi til að hefja:

• Blogg
• Forums
• Codeplex
• Twitter

Blogg

Ef þú skilur ekki RSS, stop everything and learn it. It will take 10 mínútur að læra það, kannski annað 10 mínútur til að finna vefur byggir RSS lesandi (Mér finnst Google Lesandi, www.google.com / lesandi).

Start by adding this blog to your RSS reader 🙂

Næsta, bæta www.sharepointblogs.com to your reader. They aggregate many blogs into a single feed.

Með tímanum, 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. Ef þú vilt, Ég get flutt listanum mínum og email það.

Lokum, you may want to start your own blog. I personally think that a series of blog entries describing a "newbie’s" framfarir læra WSS / MOSS væri áhugavert röð. Ég vildi að ég hefði gert það sjálfur.

Forums

Ég taka virkan þátt í tveimur umræðum hópa: MSDN og SharePoint University.

Forums are excellent places to learn. People ask questions ranging from the very simple ("How do I create a site column") til panicked ("My server is down!") til fleiri mögulegum hönnun spurningum.

Þegar þú færð bragð af umhverfinu, venture out and start replying. Short of directly interacting with a customer, ekkert er betra en þetta fyrir hendur á reynslu.

Codeplex

Fara til www.codeplex.com.

Stöðva það út og leita að SharePoint verkefnum.

Gerast áskrifandi að daglegum yfirlitssíðu Codeplex fæða í lesandi fæða.

Bæta við nýjum SharePoint verkefni að fæða lesandi þinn.

Lokum, eftir að hafa lesið í umræðunum og snúi niður eigin WSS / MOSS þína djöfla, íhuga að setja saman eigin Codeplex verkefni.

Twitter

Eins og ég skrifa þetta blogg, a einhver fjöldi af SharePoint menn hafa byrjað að nota Twitter.

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

Ályktun

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!

</enda>

Gerast áskrifandi að bloggið mitt.

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

Spjallborð notendur spyrja oft með spurningu eins og þessa:

"I would like to have a calendar at the site level that is populated by events from subsite calendars. Ideally, notendur í undirvefsvæðum mun skapa Dagskrá, 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."

Er WSS 3.0 eða Moss 2007, it is not possible to directly configure a "roll-up" calendar. Calendars exist on their own, óháð öðrum dagbók.

Til að búa til rúlla-upp dagbókina, fylgja eina af þessum leiðum:

1. Use a Content Query Web Part. This is the easiest solution for MOSS users (WSS veitir ekki CQWP). CQWP, því miður, does not provide a calendar view of data out of the box. It does provide enormous rendering flexibility (sjá hér fyrir eitt dæmi) en sjálfgefið, shows its results in simple list format. In many cases, CQWP sennilega gott val.
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 og Moss.

There are probably other clever solutions to this problem. If you have one or know of one, vinsamlegast eftir umsögn eða email mig og ég mun uppfæra þessa færslu.

</enda>

Gerast áskrifandi að bloggið mitt.

Við getum, ætti og bý margar skoðanir í SharePoint listi (skjal bókasöfn, Raða listum, o.fl.). 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 (og ég er ekki viss um að það getur), það er langt til tæknileg fyrir dæmigerður endir notandi þitt.

Ef þú vilt stjórna í hvaða röð SharePoint listi í boði skoðanir, einfaldlega prepend númer eða bréf til að skoða nafn, eins og í:

1 – Eftir tegundum Material
2 – Öll skjöl
3 – Skiladagur

-eða-

A – Eftir tegundum Material
B – Öll skjöl
C – Skiladagur

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

Z_KPI_[lýsing]

That causes my "KPI" sjónarmið að birtast neðst á listanum.

</enda>

Gerast áskrifandi að bloggið mitt.

Í dag, 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, þú stilla CQWP að tengja við gögn heimildum sínum, þá flytja það til vinnustöð, breyta <CommonViewFields>, hlaða, remove the original and now it’s ‘primed’ to display those other columns. Næsta, opna SharePoint Designer, 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. Lokum, breyta sniðmát til að gera nýja reiti! (Ekki gleyma að athuga það aftur í svo að aðrir notendur geta séð niðurstöður)."

Það er allt alveg ljóst að mér (og flestir af okkur SharePoint verktaki tegundir) hvað er að gerast og hvernig það er alveg ágætur, í raun, that the data retrieval aspects of the CQWP are so well-separate from the data presentation aspects. En, það er ekki svo auðvelt að útskýra, er það?

<endir />

To filter for a query for the Yes/No check box entitled "PG Milestone", stilla CQWP svona:

Þetta er annar einn af þeim augljós-einu sinni-þú-veist-það en harður-til-finna-að-svar-við spurningum: Hvernig á að sía á Já / Nei kassann með fyrirspurn innihald vefur hluti.

The first search result I find using the search term "filter yes/no content query web part" is flat out wrong, so I thought I’d put this up there and see if it can replace the incorrect result in typical search results.

It’s quite easy: True values = "1" and false values do not equal "1" (pretty retro, actually).

In the above example, I created site column of type "Yes/No (checkbox)" named "PG Milestone". I added it to a doc library, uploaded a few documents, set the value for a couple and tested it.

<endir />

UPDATE 12/04/07: Sjá þetta Microsoft KB (http://support.microsoft.com/kb/923589) fyrir frekari upplýsingar.

Reyndar, það kemur í ljós að það er, en tricksy MOSS þurfti að gera það erfitt.

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, en niðurstaðan er þessi:

• He tries to add a site column called "Quantity" og mosi Svör: "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. Því, "Quantity" er ekki frátekið heiti.
• He tries to find an existing site column named "Quantity" in that site collection. He cannot find it.

Ég gerði nokkrar rannsóknir, and even some coding, efldist heimspeki og að lokum komist að því að dálkinum Magn en, í raun, exist. It was in the "_Hidden" group. Hence, við gátum ekki fundið það í gegnum SharePoint notendaviðmót.

Hvernig var það fá það? I do not know, en ég hef kenningu (eða eins og konan mín myndi kalla það, "blah blah blah"). Einhvers staðar meðfram línu, a stórkostlegur fjörutíu sniðmát was added and probably activated at a site in the site collection. It was then deactivated (eða staður fjarri). The site column, þó, remained but in the "_Hidden" group. If someone knows better, vinsamlegast láttu mig vita með netfang eða staða í athugasemdum.

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) Segja að dálkur heiti er frátekið eða það er ekki. 2) Ef það er ekki áskilinn, sýna síðuna, eða að minnsta kosti að hópurinn, þar sem dálkurinn nafn er þegar í notkun.

</enda>

Í þessari viku, við afrita loks vandamál sem hafði verið greint frá a fjarlægur notandi: Þegar hún reyndi að flytja efni af lista til að skara fram úr, það virðist að byrja að vinna, en þá Excel myndi skjóta upp villa: "Cannot get the list schema column property from the SharePoint list". She was running office 2003, windows XP and connecting to MOSS.

I searched the Internets and saw some speculation but nothing 100% definitive. Hence, þessa færslu.

The problem: Exporting a view to excel that contains a date (date = the data type of the column).

What worked for us: Convert the date to a "single line of text". Þá, convert it back to a date.

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

This bug has thrown a huge shadow over the date data type in the client’s mind, so we’re going to be seeking out a definitive answer from Microsoft and hopefully I’ll post and update here in the next short period of time with their official answer and hotfix information.

Other references:

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

<enda>

Gerast áskrifandi að bloggið mitt.

Síðustu tvo daga, 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. frá markaðssetningu, nokkrir stjórnendur fulltrúi HR, Logistics, Framleiðsla, Capital Verkefni, Gæði, Innkaupastjóri, Þróunarsvið og aðrar deildir (sumir hverjir voru ekki einu sinni beinan þátt í núverandi áfanga). That’s a mighty wide audience.

Í fyrri líf mitt, 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 (sem er einhvern veginn snúið á haus hér 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.

Eins og ekkert, það er ekki fullkominn, en það er fordæmdur góður staður til að vera.

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

Neðsta lína: Ekki gera það!

Því miður, The notandi tengi gerir aðra leiðina breytingu á þeim dálki merki eins og sýnt:

Title is a column associated with the "Item" efnisgerð. Margir, margir, many CT’s use this column and if you change it here, 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’ just doesn’t make sense as a column name, 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’, every list’s title (including document libraries) changes to "Status Code" and you probably didn’t intend for that to happen.

The real problem is that this is a one-way change. The UI "knows" that "title" is a reserved word. Svo, if you try and change "Status Code" back to "Title", it will prevent you and now you’ve painted yourself into a corner using paint that never dries 🙂

So what happens if you already changed it? 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.

I have few other ideas which are on my to-do list of things to research:

• Contact Microsoft.
• Do something with the object model, maybe in conjunction with a feature.
• Figure out the database schema and manually update SQL. (You should contact Microsoft before doing this though; it will likely void your support contract).

If anyone knows how to solve this, vinsamlegast staða a athugasemd.

Update late afternoon, 11/15: I found this link that describes a method for creating a type of list that does not have a title column: http://www.venkat.org/index.php/2007/09/03/how-to-remove-title-column-from-a-custom-list/

Um viku síðan, 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.

Here are the current planned features for version 1.0: https://www.codeplex.com/Release/ProjectReleases.aspx?ProjectName=spdwfextensions&ReleaseId=8280

If anyone has any interest in this project, please leave a comment or start/add to a discussion here: http://www.codeplex.com/spdwfextensions/Thread/List.aspx

Here are the current set of functions that have been coded (though not fully tested as of 11/08/07):

Virka	Lýsing (ef ekki sama og. Hreinar virka)
NUM-færslur()	Skilar fjölda "færslur" in a string as per a specified delimiter. Til dæmis: Num-entries in a string "a,B,c" with delimiter "," = 3.
Entry()	Returns the nth token in a string as per a specified delimiter.
Lengd	String.Length
Skipta()	String.Replace()
Inniheldur()	String.Contains() Returns the word "true" or the word "false".
Hlutstreng(byrja)	String.Substring(byrja)
Hlutstreng(byrja,enda)	String.Substring(byrja,enda)
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".