UPDATE (01/17/08): Hii blog kuingia mazungumzo juu ya wema zaidi hyperlink XSL: http://www.sharepointsecurity.com/blog/sharepoint/sharepoint-2007-development/rewriting-links-in-search-results-xslt.

Overview na Lengo: I had created a simple bar chart to serve as component on a dashboard. I’ll save the details on building charts for another post, lakini sikuweza mzulia kwamba mbinu (wala alama ya swali, kwa jambo hilo). It turned out there was a bug in the chart and while I fixed that, I took the opportunity to convert some labels into hyperlinks that pointed at the underlying list behind the graph. Kwa mfano, there is a label with value "Hold". I wanted to turn the label into a hyperlink so that the user could click on it and drill down to the specific entries in the list whose status value is "Hold".

Hatua:

1. Kutumia studio ya Visual kwa SharePoint-kufahamu Intellisense.
2. Nakala DVWP ya XSLT katika studio ya Visual (kujenga mradi tupu, kuongeza faili XSL kwa mradi).
3. Nakala ya kiungo unataka kutumia katika clipboard.
4. Kuuweka katika eneo haki katika XSL.
5. Convert URL argument separators on the query string from "&" to "&Amp;"
6. Url-encode hoja ya mtu binafsi.
7. Wrap kwamba ndani ya <href…> </a>

Mfano:

Nina URL:

http://[server]/[tovuti]/Orodha / Open% 20Positions/AllItems.aspx?View ={84EEA2F5-121B-40B7-946F-0FA704A1DAA1}&FilterField1 = Recruiter&= FilterValue1 Hold

Mimi kubadili kwenye:

     <a href="Orodha / Open% 20Positions/AllItems.aspx?View =% 7b84EEA2F5-121B-40B7-946F-
0FA704A1DAA1}&Amp;FilterField1 = Recruiter&Amp;= FilterValue1 Hold">
       Kushikilia:
     </a>

Mimi manually kubadilishwa hoja ya kwanza kutoka:

{84EEA2F5-121B-40B7-946F-0FA704A1DAA1}

kwa:

%7b84EEA2F5-121B-40B7-946F-0FA704A1DAA1}

(Katika hii, brace wazi kuugeuza kwa 7b% na brace kufunga kuugeuza kwa 7d%)

Hoja ya pili na ya tatu’ vigezo ("FilterField1=Recruiter" and "FilterValue1=Kushikilia" mtiririko) hawana haja ya kuwa url-encoded kwa sababu hawana vyenye wahusika yoyote salama.

Maelezo:

Mbinu hii lazima ujumla kazi mahali popote unataka kuiweka katika hyperlink XSLT ambapo hyperlink ni pamoja na vigezo juu ya URL kama vile:

http://[server]/[tovuti]/Orodha / Open% 20Positions/AllItems.aspx?View ={84EEA2F5-121B-40B7-946F-0FA704A1DAA1}&FilterField1 = Recruiter&= FilterValue1 Hold

I got URL yenyewe kwa kupata orodha ya desturi na manually kuchuja kwenye safu ya hali ya (labeled "Recruiter" juu ya).

(Hii ni kweli umri mdogo habari, lakini kama moto favorite kituo cha kauli mbiu anatangaza, "Better late than never").

Kuangalia ni nje hapa: http://www.sharepointbeagle.com/

Kama wewe si tayari, kuwa na uhakika wa ishara ya juu.

Bila shaka, kuwa na uhakika wa kusoma yangu makala about a real-world SharePoint project (ikiwa ni pamoja na ufafanuzi mahitaji, KPI ya, maudhui ya aina, dashboards and more) as well as mwenzake yangu article about the content query web part.

Kuna mengi ya mambo mengine mazuri pia.

Mimi aliuliza swali hili karibu kila wiki, kawaida katika mazingira ya majadiliano ya usalama. An administrator/site creator has provisioned a site, kimeundwa usalama, arranged web parts and customized the quick launch to provide that oh-so-perfect set of options to the end user. Lakini, nje ya boksi, you can’t remove the "view all site content" kiungo.

Mark Wagner hutoa jibu hapa (http://www.crsw.com/mark/Lists/Posts/Post.aspx?ID=36). Yake ya kuandika-up ni kali katika ngazi mbili. Inatoa jibu la swali, "How do I remove the View All Site Content" kiungo? Kisha, ni majibu ya haraka kufuata juu ya swali: Jinsi gani mimi urahisi kuwawezesha maoni yote yaliyomo tovuti kiungo juu ya msingi tovuti-na-tovuti?

Kama ziada: Mkabala wake anafanya kazi kwa WSS, si tu MOSS.

</mwisho>

Kujiunga na blog yangu!

See UPDATE (Mimi) below (11/24/07) on How to Configure Microsoft Office SharePoint Server 2007 na Ripoti na Crawl Mtandao Folders kwa Search

Lengo: I want to execute a search restricted to a specific document library. Katika kesi hiyo, maktaba hati ina nyaraka mafunzo.

Hatua:

1. Rekodi ya URL ya maktaba hati.

2. Kujenga wigo:

Kwenda kati ya utawala.

Access the SSP.

Go to "Search Settings".

Scroll down to the scope section and select "View Scopes".

Create a new scope. Give it a name and useful description.

3. Define scope crawl rules:

Add a rule that defines the document library for this scope.

Select "web address" for "Scope Rule Type".

Enter the name of your folder (kuona #1 juu ya).

Accept the default value of "Include".

Wait for the scope to update (or start it manually).

4. Enable the scope in a site collection.

Go to site collection where you want to use this scope.

Add your new scope to the appropriate display group or groups.

5. Kutafuta!

Katika hatua hii, you’re done. Assuming the scope is properly defined, it will be available in the scopes drop downs for simple and advanced searches and when you search using that scope, you’ll just get results you expect.

Maelezo:

I wrote this blog entry because my searches for simple scope setup turned up dry using phrases like:

• configure scopes in MOSS
• configure search scope moss
• scopes in sharepoint 2007
• scopes in sharepoint
• search a document library moss
• scopes primer moss

You can create a search scope on a folder, not just the entire document library.

A scope can be shared across multiple site collections (hence, a "shared service").

You can create the scope at the site collection level itself. Hata hivyo, I prefer to go to central admin because I can start the crawl from there. You cannot start the crawl from the site collection.

UPDATE (Mimi) kama ya 11/24/07:

Kai Shang put together a great post entitled How to Configure Microsoft Office SharePoint Server 2007 na Ripoti na Crawl Mtandao Folders kwa Search @ http://kaishenghoo.spaces.live.com/blog/cns!8A7458DB12CA5AC9!206.entry

Leo, I tried to access a document library via windows explorer. This doc lib is living inside a system that consists of two WFE’s load balanced by some kind of Cisco NLB solution. (Kama / wakati wachawi mtandao niambie ni nini, Mimi itabidi update hii post).

Windows explorer couldn’t connect. I did some research and eventually, wachawi mtandao alisema kwamba WebDAV ni walemavu na / si mkono na / beneath the dignity of the NLB.

Hivyo, assuming the network wizards aren’t just telling me the network wizard equivalent of "take a long walk off a short bridge", Mimi na kushangaa — gani NLB, kwa asili, Disable WebDAV? Do we lose our windows file explorer interface to SharePoint? Is Cisco the Supu Nazi?

Microsoft creates knowledge base articles day in and day out and some of those are darned important to know about if you live in the SharePoint world.

Mimi kushika up kwa kasi na wao kupitia huduma ya kutoa na folks mzuri katika www.kbalertz.com. KBAlertz enables you to sign up for your favorite MS technology and they send you digest versions of Microsoft KB articles via email.

(UPPDATERADE 11/29 kueleza jinsi ya kupata mtandao mipangilio ya sera ya maombi kupitia UI)

I had one of those "why is MOSS doing this to me????" moments today. Katika mwisho, ni kosa wangu wote.

We have an enterprise MOSS project going on and we want to secure "place holder" sites so that no user may access it or see it. That’s easy:

1. Kwenda kwenye tovuti.
2. Kuvunja urithi usalama.
3. Kuondoa kila mtumiaji / kikundi kutoka ruhusa tovuti.

juu tuache tu mkusanyiko tovuti msimamizi na ruhusa ya kuona tovuti.

Kama mtu mwingine yeyote katika kumbukumbu, wanapaswa tena kuona tovuti na ni lazima kuwa na usalama-trimmed kutoka maeneo yote ya kawaida.

Lakini … haikuwa. Wakati huo huo, I suddenly realize that my "Joe User" standard user test account with no priv’s other than restricted read access has a "Site Actions" choice everywhere he goes. I double check one thing and double check something else. I pick up the phone to call a colleague, but put it down and check something else. I go for a walk and try everything all over again. I call a colleague and leave a message. And then, hatimaye, Mimi sioni kwamba katika Ethan ya blog, his opening graph makes it quite simple:

Moss 2007 ina kipengele mpya iitwayo Mtandao Maombi Sera. Hizi ni usalama ruhusa kwamba amefungwa kwa Maombi Mtandao. Mazingira ya usalama haya override mazingira yoyote usalama kwamba ni kuweka katika Ukusanyaji Site au Site (Mtandao) ngazi kwa mtumiaji.

A quick visit to web application policies shows that "NT Authority\authenticated users" had been granted Full Read. I removed them from the list and everything finally started working as expected. I believe they were added in the first place by someone with the mistaken impression that that is best method to grant read access to everyone in the enterprise. It does, lakini, na mnachuja quote, "It does not mean what you think it means."

Access web application policies this way:

1. Kwenda Kati Tawala
2. Kuchagua Maombi Management
3. Select "Policy for Web Application"
4. Juu ya screen kwamba, make sure you pick the correct web application. Kwa ajili yangu, ni defaults na maombi ya mtandao wa admin ya kati ambayo inaweza kuwa moja unataka.

Wakati nilikuwa na tatizo hili, I searched kwa maneno yafuatayo na got kushangaza kidogo katika suala la msaada wa moja kwa moja juu ya suala hili:

Tovuti vitendo inayoonekana kwa watumiaji wote

Tovuti vitendo inayoonekana kwa watumiaji wote

vitendo tovuti si usalama trimmed

kupata tovuti MOSS

utangulizi wa moss usalama

Tags technorati: SharePoint

Haraka na rahisi Maelekezo:

Hariri ukurasa na kuongeza Core Matokeo ya Utafutaji mtandao sehemu.

Edit that web part and expand "Fixed Keyword Query".

Kuongeza fasta Keyword swala (e.g. ContentType:"Training invoice" TrainingInvoiceNumber:1111)

Expand Results Query Options and change "Cross-Web Part query ID" to a value other than "User Query" (e.g. "Query 2").

Maelezo:

Using core search results in this manner allowed me to create a page that shows information from another site collection. The client has two major site collections: Idara na Bidhaa.

tovuti bidhaa ukusanyaji ina, kawaida ya kutosha, product information. Each product in the site collection aggregates data from multiple sources.

Moja ya idara, codes na kupima, is on such source. When users access product XYZ, they should see codes and testing data directly on the XYZ main page. Since codes and testing is hosted in another site collection, it’s a little awkward. We decided to use the core search results web part since search spans site collections. Codes and Testing manages product data via a custom list that is constrained by a specific content type. Aa keyword query that uses first the content type and then the product number narrow down the search to a single row in the custom list.

The keyword query above is an AND. It returns documents of content type "Training Invoice" and where the invoice number equals "1111".

faida nzuri kutoka kwa njia hii: We can edit the XSL from the core search results web part and generate any format that we want.

Angalia hapa (http://devcow.com/blogs/jdattis/archive/2007/04/17/SharePoint_2007_How_to_Rollup_Content_from_multiple_Site_Collections.aspx) kwa ajili ya majadiliano mwingine blogger juu ya mada hii.

</mwisho>Kujiunga na blog yangu.

Kama kudumisha blog kuwa angalau ya chini kushikamana na SharePoint, please let me know in comments. I would love to add you to my blog list.

Kama kudumisha blog kuwa si kushikamana na SharePoint lakini unataka mimi kuongeza anyway, napenda kujua. I’ll may create a separate blog list.

Please give:

• Your blog URL (wazi)
• A short description of your blog.

I want to keep the link to "active" blogs, which I’m roughly defining as one post per week and minimum three months old. If you don’t meet that "requirement" add your name to comments anyway. It’s *my* list so I can break my own rule if I want to.

Shukrani!

The client noticed a bug today with the above mentioned template.

Course managers create courses. When creating a course, meneja anges upeo wa idadi ya viti vya inapatikana.

The template provides for self-service enrollment. I enroll and a workflow attached to the registration list decrements the "available seats" haihusiani na Bila shaka kwamba.

Individuals may also unregister from a course. The bug lies here. Unregistering from a course does not increment the available seats counter. Kama matokeo, available seats is not accurate. This bug is compounded by the fact that when available seats decrements to zero, no more self-service registration is allowed.

Fortunately, Microsoft provides the workflow for this process. Even better, it’s a straight-forward workflow created via SharePoint Designer.

Follow these high level steps to fix it:

1. Fire up SDP.
2. Access the site based off the training template.
3. Access "Attendee unregistration" workflow.
4. Insert these steps (I made them the first two steps):
   1. Calculate Courses:Filled Seats minus 1 (Pato kwa Kutofautiana:calc)
   2. (kisha) Update item in Courses

Click Finish and you’re done.

Screen shots:

SharePoint Designer:

Finished workflow:

Calculate drill-down:

Update item in Courses: