UPDATE (01/17/08): Gai honi buruz informazio gehiago hiperesteka XSL bondad blog sarrera hitzaldiak: http://www.sharepointsecurity.com/blog/sharepoint/sharepoint-2007-development/rewriting-links-in-search-results-xslt.

Orokorra eta Helburua: 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, baina ez nuen asmatu teknika (ezta galdera ikurra, materia horren). 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. Adibidez, 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".

Urratsak:

1. Erabili bisuala estudioa egiteko SharePoint-jakitun intellisense.
2. Kopiatzeko DVWP en XSLT bisuala estudioan sartu (sortzeko proiektu bat hutsik, gehitu XSL fitxategi bat proiektuan).
3. Kopiatu lotura arbelera sartu erabili nahi duzun.
4. Itsatsi XSL eskuin kokapena sartu.
5. Convert URL argument separators on the query string from "&" to "&"
6. URL kodetzeko banakako argumentuak.
7. Itzulbiratu baten barruan <href bat…> </bat>

Adibidea:

URL bat dut:

http://[zerbitzaria]/[gune]/Zerrendak / Open% 20Positions/AllItems.aspx?Ikusi ={84EEA2F5-121B-40B7-946F-0FA704A1DAA1}&FilterField1 = recruiter&FilterValue1 = Eutsi

Bihurtu dut sartu:

     <bat href="Zerrendak / Open% 20Positions/AllItems.aspx?Ikusi =% 7b84EEA2F5-121B-40B7-946F-
0FA704A1DAA1}&amp;FilterField1 = recruiter&amp;FilterValue1 = Eutsi">
       Eutsi:
     </bat>

Eskuz dut eraldatu lehen argumentua tik:

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

to:

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

(Honetan, giltza irekia da, eta% 7b eraldatzen eta ixteko giltza erabilera% 7d eraldatzen)

Bigarren eta hirugarren argumentuak’ parametroak ("FilterField1=Recruiter" and "FilterValue1=Eutsi" hurrenez hurren) ez da beharrezkoa izango URL-kodetuta ez dutelako eduki unsafe pertsonaiak edozein.

Oharrak:

Teknika hau, oro har, edozein lekutan lan bat XSLT en hiperesteka non Hiperesteka hartzen ditu, besteak beste, parametro gisa URL gainean txertatu nahi duzun:

http://[zerbitzaria]/[gune]/Zerrendak / Open% 20Positions/AllItems.aspx?Ikusi ={84EEA2F5-121B-40B7-946F-0FA704A1DAA1}&FilterField1 = recruiter&FilterValue1 = Eutsi

URL bera lortu nuen zerrenda pertsonalizatu sartzeko eta eskuz egoera zutabean iragazketa (labeled "Recruiter" Goiko).

(Hau da, benetan pixka bat zaharra albisteak, baina nire sua geltokia lema gisa aldarrikatzen, "Better late than never").

Begira hemen: http://www.sharepointbeagle.com/

Izan ez baduzu, ziur egon saioa hasi.

Jakina, ziurtatu irakurri nire artikulu about a real-world SharePoint project (eskakizunen definizioa barne, KPI en, eduki mota, dashboards and more) as well as nire lankide-en article about the content query web part.

Bada ona beste gauza asko da, gehiegi.

Ez dut galdera hau ia aste guztietan, normalean segurtasun eztabaida baten testuinguruan. An administrator/site creator has provisioned a site, konfiguratuta segurtasun, arranged web parts and customized the quick launch to provide that oh-so-perfect set of options to the end user. Baina, koadroan out, you can’t remove the "view all site content" lotura.

Mark Wagner erantzuna ematen du hemen (http://www.crsw.com/mark/Lists/Posts/Post.aspx?ID=36). Bere idazteko-up da emanaldirik bi mailatan. Erantzun bat ematen du, galdera, "How do I remove the View All Site Content" lotura? Gero, berehala erantzuten jarraitu-galdera: Nola gaitu erraz dut ikuspegi guztiak gune eduki site-by-gune oinarri esteka?

Bonus gisa,: Bere planteamendu WSS lanak, ez bakarrik MOSS.

</amaiera>

Nire blog Harpidetu!

See UPDATE (I) below (11/24/07) an Nola Microsoft Office SharePoint Zerbitzaria konfiguratzeko 2007 Aurkibidea eta arakatzea Network Search for karpetak

Helburua: I want to execute a search restricted to a specific document library. Kasu honetan, Dokumentu liburutegia dauka prestakuntza dokumentuak.

Urratsak:

1. Grabatzeko dokumentua liburutegian URL.

2. Sortu hedadura:

Administrazio Zentralari joan.

Sartzeko SSP du.

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. Zehaztu arakatze arau esparrua:

Gehitu arau bat da, dokumentu liburutegia definitzen esparrua honetan.

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

Idatzi zure karpeta-izena (ikusi #1 Goiko).

Accept the default value of "Include".

Esparrua itxaron eguneratu (hasteko edo eskuz).

4. Gaitu esparrua gune bilduma batean.

Gunean bilduma Joan esparrua hau erabili nahi duzu.

Gehitu zure esparrua egokia pantaila talde edo talde.

5. Bilatu!

Puntu honetan, you’re done. Assuming the scope is properly defined, erabilgarri izango den esparru jaitsiera bilaketak sinple eta aurreratuentzako gorabeherak eta noiz erabiltzen duten esparrua bilatu, besterik ez dituzu lortuko emaitzak espero.

Oharrak:

Blog sarrera hau idatzi nuen nire esparrua simple konfigurazioa bilatzen gaurkoan delako lehorra erabiliz esaldiak bezala:

• konfiguratzeko esparru MOSS en
• konfiguratzeko bilaketa-esparrua goroldioa
• SharePoint-en esparru 2007
• SharePoint-en esparru
• bilatu dokumentu liburutegia goroldioa
• Esparru lehen goroldioa

Bilaketa-esparrua bat sor dezakezu karpeta batean, not just the entire document library.

Esparrua A gune anitz bildumak zehar parteka daitezke (beraz,, a "shared service").

You can create the scope at the site collection level itself. Hala eta guztiz ere, 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 (I) gisa 11/24/07:

Kai Shang put together a great post entitled Nola Microsoft Office SharePoint Zerbitzaria konfiguratzeko 2007 Aurkibidea eta arakatzea Network Search for karpetak @ http://kaishenghoo.spaces.live.com/blog/cns!8A7458DB12CA5AC9!206.entry

Gaur egun, 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. (/ Denean sare morroiak esango dit zer den, Post hau eguneratuko dut).

Windows explorer couldn’t connect. I did some research and eventually, sare morroiak esan WebDAV desgaituta dago arabera / ez du onartzen / beneath the dignity of the NLB.

Beraz,, assuming the network wizards aren’t just telling me the network wizard equivalent of "take a long walk off a short bridge", Galdetzen daukat — du NLB, Naturak, desgaitu WebDAV? Do we lose our windows file explorer interface to SharePoint? Is Cisco the Zopa nazien?

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.

Jarraitu nuen haiekin bizkortzeko zerbitzu baten bidez ona Folks hornitu at 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.

(EGUNERATUA 11/29 nola web aplikazio politika ezarpenak sartzeko azaltzeko UI bidez)

I had one of those "why is MOSS doing this to me????" moments today. Azkenean, Nire errua da guztia.

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. Gunera joan.
2. Break segurtasun ondarea.
3. Kendu erabiltzaile bakoitzak / talde baimenak gune batetik.

Gainetik besterik gune-administratzaile-bilduma utzi behar baimena gune ikusi nahi dituzten.

Inork egunkaria bada, ez da gehiago behar dute ikusi gune eta izango da, ohiko leku guztietako segurtasun-moztutako.

Baina … ez zen. Aldi berean,, 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, azkenik, Dut aurkitu duen Ethan bloga, his opening graph makes it quite simple:

Moss 2007 izeneko web aplikazioa politikak ezaugarri berri bat dauka. Horiek segurtasun-baimen hori web aplikazio lotuta daude. Segurtasun ezarpen horiek baliogabetzeko edozein segurtasun-ezarpen bat da, bilduma, edo Web Gunearen ezarri (Web) erabiltzaile maila.

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, baina, Aurrekontu bat iragazi nahi, "It does not mean what you think it means."

Access web application policies this way:

1. Administrazio Zentralari joan
2. Aukeratu Gestión
3. Select "Policy for Web Application"
4. Pantaila horretan, make sure you pick the correct web application. Niretzat, lehenetsi admin erdiko aplikazio web eta horrek agian ez da nahi duzuna da.

Noiz arazo hori izan nuen, Bilatuko du ondorengo esaldi dut eta lortu harrigarriro txiki zuzeneko laguntza dagokionez gai honetan:

Gune ekintzak erabiltzaile guztientzat ikusgai

Gune ekintzak erabiltzaile guztientzat ikusgai

gune ekintzak ez dira segurtasun-moztutako

ziurtatzeko MOSS gune bat

to goroldioa segurtasun sarrera

Technorati Tags: SharePoint

Azkarra eta sinplea jarraibideak:

Aldatu orri bat eta bilatu Core emaitzak web zati gehitu.

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

Gehitu finkoa keyword kontsulta (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").

Oharrak:

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: Sailak eta Produktuak.

Produktuaren gune bilduma dauka, naturalean nahikoa, product information. Each product in the site collection aggregates data from multiple sources.

Sail bat, kodeak eta azterketa, 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".

Planteamendu honek onura atsegina: We can edit the XSL from the core search results web part and generate any format that we want.

Ikusi hemen (http://devcow.com/blogs/jdattis/archive/2007/04/17/SharePoint_2007_How_to_Rollup_Content_from_multiple_Site_Collections.aspx) Blogger beste gai honi buruzko eztabaida.

</amaiera>Nire blog Harpidetu.

Mantentzen baduzu, blog bat bada, hori gutxienez minimoki to SharePoint konektatuta, please let me know in comments. I would love to add you to my blog list.

Mantentzen baduzu, blog bat ez dela SharePoint konektatuta badago, baina nahi gehitzeko Niri hala ere, let me know. I’ll may create a separate blog list.

Please give:

• Your blog URL (jakina,)
• 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.

Eskerrik asko!

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

Course managers create courses. When creating a course, kudeatzailea eserleku eskuragarri gehienezko kopurua zehazten du.

The template provides for self-service enrollment. I enroll and a workflow attached to the registration list decrements the "available seats" ikastaro lotutako.

Individuals may also unregister from a course. The bug lies here. Unregistering from a course does not increment the available seats counter. Baten ondorioz, available seats is not accurate. This bug is compounded by the fact that when available seats decrements to zero, ez gehiago auto-zerbitzua erregistroa onartzen da.

Zorionez, Microsoft provides the workflow for this process. Even better, SharePoint Designer bidez sortzen zuzen Aurrera workflow bat da.

Jarraitu horiek maila handiko urratsak konpondu:

1. Sua sortu SDP.
2. Sartzeko prestakuntza plantilla off oinarritzen Gunean.
3. Access "Attendee unregistration" workflow.
4. Txertatu urrats hauek (Horietako lehen bi urrats egin nuen):
   1. Kalkulatzeko Ikastaroak:Bete estaliak ken 1 (Irteera Aldakorra:calc)
   2. (ondoren,) Eguneratu elementu Ikastaroak

Egin klik Amaitu eta Bukatutakoan.

Pantaila plano:

SharePoint Designer:

Amaitu workflow:

Kalkulatzeko zulatzeko-behera:

Eguneratu elementua Ikastaroak: