УПДАТЕ: 04/25/08: Је сустижу на неким блогу и нашао линк на овај чланак: 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.

У последњих неколико месеци, a dozen or more folks from across the planet have been emailing me and asking the general question, "How do I learn SharePoint?"

I’m hardly authoritative, but I’ve had some success (and trying to get better all the time) so I thought I’d document my personal road map. Others may find it valuable.

Before I do that, I just want to observe that it’s obvious to me, based on these personal emails and the even greater number of MSDN / SharePoint University posts of the same nature, 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 … easier to find good SharePoint talent? 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’s 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.

Some Basic Terms

For people entering this world, there are two key acronyms:

• ВСС: Windows SharePoint Services
• МОСС: Мицрософт Оффице СхареПоинт Сервер

WSS is "free" in that it’s bundled with windows server 2003 (or at least can be downloaded from MS). I put quotes around free because you need a box, a valid O/S license and probably SQL (though there’s a "free" kind of SQL as well).

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

Perhaps not day one, but soon after you’ve got some basic familiarity with the platform, it’s important to learn the differences. На пример, a powerful web part, the Content Query 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 the Books

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, I purchased the two books listed here (http://paulgalvin.spaces.live.com/lists/cns!1CC1EDB3DAA9B8AA!203/).

I started with the big blue administration book. Naturally, it covers administration. Истовремено, it provides a survey of all MOSS features (and WSS features as well).

За мене, it’s not so important to remember all the various details (until it’s time to get certified) but it’s good to know the boundaries. (I follow this same approach in 1st person shooters I play on the xbox or 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.)

After reading the big blue book, I would read the entire Inside WSS book. It dives deeply into issues that developers care most about.

Create a Virtual Environment

In order to do any development or properly use the environment, you need a full blown windows server operating system with SharePoint Designer, Висуал Студио 2005 (2008 works, but some useful tools have yet to be ported as of the writing of this article), ИнфоПатх 2007 and some other stuff. There are many good blog entries describing this process. I’d have a look at these two:

• How to Create a MOSS 2007 VPC Image: The Whole 9 Yards – SharePoint Reporter Blog
• How to build an optimal developer VPC for SharePoint Development – Blog

Додатно, Andrew Connell shared his experiences with VMWare here:

• Microsoft’s virtualization products vs. VMWare’s offerings

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. Али … don’t bother blogging about it or posting it to MSDN forums. It’s already been done 🙂. Уместо тога, embrace it and move on. You’ll be better off for it.

Get Certified

I believe that the MS SharePoint certification path, which consists four exams, is exhaustive. I suggest that you follow their online preparation guide and do your best to understand each of the areas of the test.

Ја do not suggest that you take the exam just to pass it. Ја do not suggest that you use one of the "brain dump" style 3rd party "tools" for passing MS tests. If you can take the test, pass it based on a combination of your own directed study and hands-on experience, you’ll be a stronger developer and job candidate for it.

There are four tests in two "tracks":

Developer:

• TS: Мицрософт Виндовс СхареПоинт Сервицес 3.0 – Развој апликација
• TS: Мицрософт Оффице СхареПоинт Сервер 2007 – Application Development

Admin:

• TS: Windows SharePoint Services 3.0, Configuring
• TS: Мицрософт Оффице СхареПоинт Сервер 2007, Configuring

I recommend that developers study for all of these exams. You’ll be strong for them, though I suppose if you skipped the admin exams, you would get by.

I found the WSS version to be considerably more challenging than the corresponding MOSS versions, much to my surprise. I was in a class recently and several others made the same point.

While I was studying for the 70-542 испит (MOSS development) 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 Into the Community

The SharePoint community is vibrant, strong and growing larger all the time.

You want to look at the following to start:

• Blogs
• Форум
• Цодеплек
• Цвркут

Blogs

If you don’t understand RSS, stop everything and learn it. It will take 10 minutes to learn it, maybe another 10 minutes to find a web based RSS reader (I like google’s reader, www.google.com/reader).

Start by adding this blog to your RSS reader 🙂

Следећи, add www.sharepointblogs.com to your reader. They aggregate many blogs into a single feed.

Over time, 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. If you want, I can export my list and email it.

Коначно, you may want to start your own blog. I personally think that a series of blog entries describing a "newbie’s" progress learning WSS/MOSS would be an interesting series. I wish I had done that myself.

Форум

I actively participate in two forum groups: MSDN and SharePoint University.

Forums are excellent places to learn. People ask questions ranging from the very simple ("How do I create a site column") to the panicked ("My server is down!") to more hypothetical design questions.

Once you get a flavor of the environment, venture out and start replying. Short of directly interacting with a customer, nothing is better than this for hands on experience.

Цодеплек

Иди на www.codeplex.com.

Check it out and search for SharePoint projects.

Subscribe to the daily summary Codeplex feed in your feed reader.

Add any new SharePoint projects to your feed reader.

Коначно, after reading the forums and facing down your own WSS/MOSS demons, consider putting together your own codeplex project.

Цвркут

As I write this blog entry, a lot of SharePoint folk have started using Цвркут.

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

Conclusion

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!

</крај>

Претплатите се на мој блог.

УПДАТЕ: An anonymous person in the comments posts this link: http://www.atidan.com/atidan-collaboration-kit.php

Форум корисници често питам овако:

"I would like to have a calendar at the site level that is populated by events from subsite calendars. Ideally, корисници у подсајтова ће створити догађаје из календара, 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."

Да ли је ВСС 3.0 или МОСС 2007, it is not possible to directly configure a "roll-up" calendar. Calendars exist on their own, независно од било ког другог календара.

Да бисте направили ролл-уп календара, пратите једну од тих путева:

1. Use a Content Query Web Part. This is the easiest solution for MOSS users (ВСС не пружа ЦКВП). ЦКВП, нажалост, does not provide a calendar view of data out of the box. It does provide enormous rendering flexibility (погледајте овде на једном примеру) већ по дефаулту, shows its results in simple list format. In many cases, ЦКВП вероватно добар избор.
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 и маховине.

There are probably other clever solutions to this problem. If you have one or know of one, оставите коментар или пошаљи ми и ја ћу ажурирати овај пост.

</крај>

Претплатите се на мој блог.

Можемо, треба и да створе многе погледе на СхареПоинт листама (библиотеке докумената, Прилагођене листе, итд). 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 (и нисам сигуран да може), далеко је до техничких типичне за крајњег корисника.

Ако желите да контролишете редослед којим СхареПоинт листама доступне виевс, једноставно препенд број или писмо видите име, као у:

1 – По материјалу
2 – Сви документи
3 – Датум доспећа

-или-

A – По материјалу
Б – Сви документи
Ц – Датум доспећа

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

З_КПИ_[опис]

That causes my "KPI" погледа да се појави на дну листе.

</крај>

Претплатите се на мој блог.

Данас, 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, конфигурисања ЦКВП да се повезује са њеним изворима података, онда га извезете на вашем радном месту, модификовати <ЦоммонВиевФиелдс>, отпремање, remove the original and now it’s ‘primed’ to display those other columns. Следећи, отворити СхареПоинт Десигнер, 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. Коначно, измените шаблон да донесе своје нове поља! (Не заборавите да проверите поново тако да остали корисници могу да виде резултате)."

Све је потпуно јасно (и већина од нас СхареПоинт девелопер врсте) шта се дешава и како је то сасвим лепо, заиста, that the data retrieval aspects of the CQWP are so well-separate from the data presentation aspects. Али, то није тако лако објаснити, да ли је?

<крај />

To filter for a query for the Yes/No check box entitled "PG Milestone", конфигурише ЦКВП овако:

Ово је још једна од оних очигледан-када-си-знате-то, али тешко наћи-на-одговор-питања: Како за филтрирање на ДА / НЕ потврду помоћу Веб сегмента упита садржаја.

Први Резултат претраге I find using the search term "filter yes/no content query web part" стан је погрешна, па сам помислио бих ставио ово горе и види да ли може да замени неисправну резултат у типичним резултатима претраге.

То је прилично лако: True values = "1" and false values do not equal "1" (прилично ретро, заправо).

У горњем примеру, I created site column of type "Yes/No (поље за потврду)" named "PG Milestone". I added it to a doc library, отпремио неколико докумената, поставите вредност за пару и тестирали га.

<крај />

УПДАТЕ 12/04/07: Видети this Microsoft KB (http://support.microsoft.com/kb/923589) for related information.

Заправо, it turns out it is, али 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, but the end result is this:

• 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. Стога, "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, заправо, 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"). Негде дуж линије, a 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, међутим, remained but in the "_Hidden" group. If someone knows better, please let me know via е-маил 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.

</крај>

Ове недеље, смо коначно репродуковати проблем који је пријављен од стране удаљеног корисника: Када је покушала да извози садржај листе у Екцел, ствари би било да почну да раде, али онда це се појавити за Екцел грешку: "Cannot get the list schema column property from the SharePoint list". She was running office 2003, windows XP and connecting to MOSS.

Тражио сам на Интернетс и видела неке спекулације, али ништа 100% definitive. Hence, овај пост.

Проблем: Извоз у Екцел приказ који садржи датум (датум = тип података у колони).

Шта је радио за нас: Convert the date to a "single line of text". Онда, конвертовати га назад до датума.

That solved it. It was nice to see that the conversion worked, заправо. It was quite nervous that converting things this way would fail, but it did not.

Овај буг је бачена велику сенку података датуму типа у виду клијента, па ћемо да се траже од дефинитивног одговора из Мицрософта, и надам се да ћу писати и ажурирате овде у наредном кратком временском периоду са њиховог званичног одговора и хитних информација.

Остале референце:

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

<крај>

Претплатите се на мој блог.

Током последња два дана, 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. из маркетинга, представљају директори неколико ХР, Логистика, Производња, Капитални пројекти, Квалитет, Куповина, Корпоративни развој и других одељења (од којих су неки директно укључени ни у садашњој фази). That’s a mighty wide audience.

У мом претходном животу, 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 (који се некако окренуо наглавачке овде 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.

Као и било шта, није савршен, али је проклето добро место да се.

На СхареПоинт блог, someone occasionally asks about "changing the label of Title" or about "removing title from lists".

Боттом лине: Немој то да радиш!

Нажалост, кориснички интерфејс омогућава једносмерну промену те колоне ознаци као што је приказано:

Title is a column associated with the "Item" тип садржаја. Многи, многи, многи ЦТ користе ову колону, а ако га промените овде, 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’ једноставно нема смисла као име колоне, 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’, Свака листа наслов (укључујући библиотеке докумената) changes to "Status Code" и вероватно није намеравао да се то деси.

Прави проблем је у томе што је то једносмерна промена. The UI "knows" that "title" is a reserved word. Тако, if you try and change "Status Code" back to "Title", то ће вас спречити и сада сте насликао себе у ћошак using paint that never dries 🙂

Дакле, шта се дешава ако сте већ га променили? 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.

Имам још неке идеје које су на мојој то-до листа ствари за истраживање:

• Контакт Мицрософт.
• Урадите нешто са објектним моделом, Можда у комбинацији са функцијом.
• Схватите шему базе података и ручно ажурирање СКЛ. (Требало би да контактирате Мицрософт пре него што ово ипак; вероватно ће поништити уговор за подршку).

Ако неко зна како да се реши ово, пошаљите коментар.

Упдате касно поподне, 11/15: Нашао сам овај линк који описује метод за стварање тип листе који нема колону титулу: http://www.venkat.org/index.php/2007/09/03/how-to-remove-title-column-from-a-custom-list/

Пре око недељу дана, 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.

Овде су актуелне карактеристике планиране за верзију 1.0: https://www.codeplex.com/Release/ProjectReleases.aspx?ProjectName=spdwfextensions&ReleaseId=8280

Ако неко има било какав интерес у овом пројекту, оставите коментар или старт / додај у дискусији овде: http://www.codeplex.com/spdwfextensions/Thread/List.aspx

Ево тренутни сет функција које су кодиране (мада не у потпуности тестирани од 11/08/07):

Функција	Опис (ако не и исто као Нето функција.)
Број ставки-()	Returns the number "entries" in a string as per a specified delimiter. На пример: Num-entries in a string "a,Б,Ц" with delimiter "," = 3.
Улазак()	Returns the nth token in a string as per a specified delimiter.
Дужина	Стринг.Ленгтх
Заменити()	Стринг.Реплаце()
Садржи()	Стринг.Цонтаинс() Returns the word "true" or the word "false".
Субстринг(почетак)	Стринг.Субстринг(почетак)
Субстринг(почетак,крај)	Стринг.Субстринг(почетак,крај)
ТоУппер()	Стринг.ТоУппер()
ТоЛовер()	Стринг.ТоЛовер()
СтартсВитх()	Стринг.СтартсВитх() Returns the word "true" or the word "false".
ЕндсВитх()	Стринг.ЕндсВитх() Returns the word "true" or the word "false".