Svo, this morning, my son is determined to see an age-thirteen restricted Halo 3 video at Gamespot. I’m outside shoveling snow, so I’m not there to help or hinder. Necessity is the mother of invention and all that … he has a eureka! moment. He realizes that even though Gamespot wants him to enter his real birth date, he can actually enter allir birth date he wants. Once he realized that, he made himself old enough to see the video.
I’m not quite sure how I feel about this 🙂
At my first job out of college in 1991, I was lucky to to work for a manufacturing company with 13 stöðum, not including its corporate HQ in New Jersey. I joined just when the company was rolling out a new ERP system. We were a small IT department of about ten people altogether, two of whom Did Not Travel. Part of the project involved replacing IBM System 36 boxes with HP hardware and HPUX. Everyone used green tubes to access the system.
The project rolls along and I’m sent down to Baltimore with a new co-worker, Jeff. Our job was to power up the Unix box, make sure the O/S was running, install the ERP system, configure the ERP, train people on the ERP and do custom work for folks on the spot. (This was a dream job, especially coming straight out of college). Before we could really get off the ground, we needed to unpack all the green tubes, put them on desks and wire them. And the best part was that we had to put the RJ11 connectors on ourselves.
For some reason that I never understood and actually never thought to ask about at the time, we had had some contracting company come along and run cable throughout the plant, but we didn’t have them put on the connectors. Svo, there was a "patch box" with dozens of of unlabeled cables in the "computer room" and these snaked around the building to various places in the building.
We worked our way through it over the course of a weekend, testing each wire, putting on a connector (making sure it was straight vs. crossed), ensuring the bit settings on the green tubes and printers were correct, labeling wires, making sure that "getty" was running correctly for each port and probably a thousand other things that I’ve suppressed since then. It all came together quite nicely.
En, there was one important cable that we couldn’t figure out. The plant in Baltimore had a relationship with a warehousing location in New Jersey. Some orders placed in Baltimore shipped out of that location. There were two wires that we had to connect to the HPUX box: a green tube and a printer. The green tube was easy, but the printer turned into a three-week nightmare.
If you don’t know it, or have suppressed it, dealing with green tubes and printers this way, there are various options that you deal with by setting various pins. 8-hluti, 7-hluti, parity (even/odd/none), probably others. If you get one of those settings wrong, the tube or printer still shows stuff, but it will be total gibberish, or it will be gibberish with a lot of recognizable stuff in between. Auðvitað, these pins are hard to see and have to be set by using a small flat-edge screw driver. And they are never standard.
We set up the first of many quick calls with the NJ guy (a grizzled computer hater who probably curses us to this day). We got the green tube working pretty quickly, but we couldn’t get the printer to work. It kept "printing garbage". We would create a new RJ11 connector, switching between crossed and straight. We would delete the port and re-created in Unix. We went through the arduous task of having him explain to us the pin configuration on the printer, never really sure if he was doing it correctly.
It’s about time to go live, everything in Baltimore is humming, but we can’t get the cursed printer up in NJ to work! We’ve exhausted all possibilities except for driving back up to NJ to work on the printer in person. To avoid all that driving, we finally ask him to fax us what he’s getting when it’s "garbage", hoping that maybe there will be some clue in that garbage that will tell us what we’re doing wrong.
When we got the fax, we immediately knew what was wrong. Sjá, our method of testing whether we had configured a printer correctly was to issue an "lp" command like this:
lp /etc/passwd
Grundvallaratriðum, we printed out the unix password file. It’s always present and out of the box, always just one page. You standard Unix password file looks something like this:
smith:*:100:100:8A-74(office):/home/smith:/usr/bin/sh guest:*:200:0::/home/guest:/usr/bin/sh
We had been printing out the password file over and over again for several weeks and it was printing correctly. Hins, to the end user, it was "printing garbage".
</enda>
My client recently installed a magic device from Juniper that apparently replaced their old Cisco network load balancer (NLB). At about the same time, we installed a hotfix to address a workflow problem.
A day or two later, we noticed a problem when we accessed the shared service provider (SSP). We could get to it, but we would be challenged for a user ID and password many times on each page. This didn’t happen with the main portal app, nor central administration. Naturally, we didn’t know which of the two (Juniper or hotfix) would be the issue, though I strongly suspected the hotfix, figuring we had not installed it quite right.
It turned out that Juniper had some kind of compression setting. Eitt af því sem robed figures over in the network group turned that setting off. That solved our problem.
This is not the first time that compression has been the root cause of a SharePoint problem for me. IIS compression adversely affected a 3rd party tool from the good people at The Dot Net Factory for IE 6 browsers (IE 7 browsers worked without difficulty).
Svo, add "compression" to the hazards list.
</enda>
Credit to: http://www.elfwood.com/art/s/h/sherry/death_colour.jpg.html
I started off my "blogging career" using Microsoft’s platform and it’s been good to me. It’s easy to post, there are good options and widgets for managing your "space", decent web storage and so forth.
Hins, I really just fell into the MS solution with almost no planning. That alone calls for me to evaluate where I am and where I’m going, in terms of a blogging platform. There are also two important limitations that bother me right now vis-à-vis Windows Live Spaces.
Fyrsta, I can’t get very good statistics. There are stats but the detail is often truncated and not presented in a way that allows for any kind of analysis. There no sorting or export capability. I get many blog ideas based on the kind of information people find (or especially fail to find) when they search my blog. It’s very hard to use lives spaces for that.
Annað, there does not seem to be any mechanism to "monetize" a windows live space blog. Í raun, in order to get rid of MS ads (from which I derive no benefit), I need to actually pay Microsoft. (At least, that’s how I understand it; I have been unable to get definitive answers to this and questions like it).
Now that I’ve got an established pattern and set of blogging habits, I want to evaluate other options. I’ve done some research and there are a lot of choices, but I’m curious as to what other people, particularly others in the SharePoint community (as bloggers or readers), like to use.
If this subject interests you and you have an opinion or are willing to share your experience, please leave a comment or email me directly.
Takk!
<endir />
Forum users occasionally ask: Why does SharePoint Designer put ???? into my email instead of a field value?
One reason this happens is because the variable to which you refer is null.
This can happen because you are trying to reference a field from the "current item" but the user never entered a value into that form field.
<endir />
Atburðarás: Í SharePoint Designer workflow, you need to determine if a date field is blank.
Vandamál: SPD does not provide a direct method for comparing dates to anything other than a date. You cannot create a condition like this: "If [Date Field] equals blank".
Lausn: Convert the date to a string. Use string comparison to determine if the date is blank.
Skjár skot:
The following screen shots show how to do this. Í þessari atburðarás, reit á hlut, "Environmental Permits:First Permit Reminder Date", er lögð og workflow eldar í svar.
Skýringar:
Þegar ég reyndi þetta, I was pleasantly surprised to learn that it works. I was worried that SharePoint Designer might disallow the string assignment (Variable:StringReminderDateDate) en það gerði leyfa það.
Ég var líka áhyggjur af því að leyfa það, verðmæti gæti verið tómt og annaðhvort blása upp WF á afturkreistingur eða kannski hækka á heimsvísu 1/2 gráðu, en þær grunsemdir voru ástæðulausar.
</enda>
Í 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 />
Út af the kassi, Moss’ Efni Fyrirspurn Web Part (CQWP) birtir uppgjör sitt á lista sniði, similar to search results. It is also possible to display the results in a grid format (i.e. HTML töflu snið). Grid formats are better in some circumstances. I describe how to achieve that effect in this article.
I have worked with a client on an enterprise-wide MOSS rollout. We have designed their taxonomy such that projects are first class citizens in the hierarchy and have their own top level site. Project managers maintain a singleton list of project summary information, svo sem titil, fjárhagsáætlun, ráð verklok, remaining budget and other summary type fields. By "singleton" I mean a custom SharePoint list guaranteed to contain only one item. Simplistically, það lítur svona út:
Tæknilega nálgun er mikill the sami eins og lýst hér (http://paulgalvin.spaces.live.com/blog/cns!1CC1EDB3DAA9B8AA!447.entry). The CQWP uses an XSL transform to emit HTML for the browser to render.
I always envision the result before diving into the XSL because XSL is a nightmare. Here’s my desired result:
HTML svona býr að niðurstöðu:
<HTML> <líkami> <miðstöð> <borð landamæri= 1> <!-- Merki -> <tr bgcolor= Blár> <td><letur litur= Hvítt><B>Project Name</B></letur></td> <td align= Rétt><letur litur= Hvítt><B>Ljúka Dagsetning</B></letur></td> <td align= Rétt><letur litur= Hvítt><B>Budget</B></letur></td> <td align= Rétt><letur litur= Hvítt><B>Raunveruleg kostnað</B></letur></td> <td><letur litur= Hvítt><B>Alls Status</B></letur></td> </tr> <tr> <td>Re-vír tölvu herbergi.</td> <td align= Rétt>02/01/08</td> <td align= Rétt>22,500.00</td> <td align= Rétt>19,000.00</td> <td>Í vinnslu</td> </tr> <tr> <td>Framlag netþjóna fyrir SQL Uppfærsla</td> <td align= Rétt>04/01/08</td> <td align= Rétt>7,500.00</td> <td align= Rétt>0.00</td> <td>Planned</td> </tr> </borð> </miðstöð> </líkami> </HTML> |
Fylgdu þessum skrefum til að búa rist:
I’m going to concentrate on number six. Numbers one through four are straight-forward and something that any CQWP user has already done. Number five has been well-documented by others including this exhaustive screen-shot laden article from MSDN hér (http://msdn2.microsoft.com/en-us/library/bb897399.aspx) og bloggið Heather Salómons hér (http://www.heathersolomon.com/blog/articles/CustomItemStyle.aspx).
Byrja og framkvæma skref eitt til fimm eins og á MSDN skjöl og greinar Heather Salómons.
Á þessum tímapunkti, þú bættir CQWP til síðu og þú hafa þinn <CommonViewFields> stillt eftir þörfum.
Eftir venjulega skrefum, Ég fæ þessar millistig niðurstöður:
1. Búa gerð efnis, a templatized custom list for that content type and two sites. Here is the content type:
Hér er síða uppbygging:
2. Bæta við CQWP eftir að búa verkefni undirvefsvæðum mínar og Singleton verkefnisins samantekt listi:
3. Bæta allar frekari upplýsingar sem ég vil í gegnum <CommonViewFields>:
<eign nafn="CommonViewFields" tegund="band">Project_x0020_Name;Project_x0020_Expenses;Project_x0020_Status;Project_x0020_Start_x0020_Date;Project_x0020_End_x0020_Date;Project_x0020_Budget</eign>
Athugaðu að ég þurfti að halda öllum eignum reiti í einni línu eða það myndi ekki virka (CQWP myndi segja mér að fyrirspurn skilað engar vörur).
4. Á þessum tímapunkti, we’re ready to move beyond the MSDN article and flip on over to Heather Solomon’s article. Follow her steps starting near step #5 til að búa til sérsniðna / unghosted version of ItemStyle.xsl. I follow Heather’s advice, upp í gegnum skref 11 og fá þessir millistig niðurstöður:
4.1: Nafn XSL sniðmát mitt eftirfarandi:
<XSL:template name="Grid" match="Row[@Style=’Grid’]" mode="itemstyle">
Ég líka örlítið breytt henni leiðbeinandi <XSL:fyrir-hvern …> með því að bæta <br /> merkja að veita hreinni skráningu:
<XSL:fyrir-hvern velja="@ *"> P:<XSL:gildi-af velja="nafn()" /><br/> </XSL:fyrir-hvern>
4.2: Ég breyta vefur hluti, go to appearance and select my "Grid" stíl:
Sækja breytinguna og hér er útkoman:
Við sjáum af ofangreindu að reitir við viljum (Verkefnið nafn, kostnað, staða, o.fl.) are available for us to use when we emit the HTML. Not only that, but we see the names by which we must reference those columns in the XSL. Til dæmis, we reference Project Status as "Project_x005F_x0020_Name".
Á þessum tímapunkti, við víkja úr blogginu lyngi og frá herðum þessara risa, Ég bæta við eigin svolítið minn.
ATHUGIÐ: Þegar að gera breytingar á bæði ContentQueryMain.xsl auk ItemStyle.xsl, þú þarft að athuga þær skrár aftur í áður en þú sjá áhrif af breytingum þínum.
Fyrir rist-gerð tilgangi, MOSS uses two different XSL files to produce the results we see from a CQWP. To generate the previous bit of output, we modified ItemStyle.xsl. MOSS actually uses another XSL file, ContentQueryMain.xsl to in conjunction with ItemStyle.xsl to generate its HTML. As its name implies, ContentQueryMain.xsl is the "main" XSL that controls the overall flow of translation. It iterates through all the found items and passes them one by one to templates in ItemStyle.xsl. We’ll modify ItemStyle.xsl to generate the open <borð> skipun á undan emitting fyrstu röðinni af gögnum og lokun <borð> tag after emitting the last row. To accomplish this, ContentQueryMain.xsl is modified to pass two parameters to our "grid" sniðmát í ItemStyle.xsl, "last row" and "current row". ItemStyle.xsl uses these to conditionally emit the necessary tags.
Notkun tækni Heather Salómons, we locate ContentQueryMain.xsl. It is located in the same place as ItemStyle.xsl. This screen shot should help:
Við þurfum að gera eftirfarandi breytingar:
Locate the template named "OuterTemplate.CallItemTemplate" auðkennd með streng:
<XSL:sniðmát nafn="OuterTemplate.CallItemTemplate">
Settu alla sniðmát sem fylgir:
<XSL:sniðmát nafn="OuterTemplate.CallItemTemplate"> <XSL:Gildi nafn="CurPosition" /> <!-- Add the "LastRow" breytu. We only use it when the item style pass in is "Grid". --> <XSL:Gildi nafn="LastRow" /> <XSL:velja> <XSL:þegar próf="@ Style = 'NewsRollUpItem'"> <XSL:gilda-sniðmát velja="." ham="itemstyle"> <XSL:með-Gildi nafn="EditMode" velja="$cbq_iseditmode" /> </XSL:gilda-sniðmát> </XSL:þegar> <XSL:þegar próf="@ Style = 'NewsBigItem'"> <XSL:gilda-sniðmát velja="." ham="itemstyle"> <XSL:með-Gildi nafn="CurPos" velja="$CurPosition" /> </XSL:gilda-sniðmát> </XSL:þegar> <XSL:þegar próf="@ Style = 'NewsCategoryItem'"> <XSL:gilda-sniðmát velja="." ham="itemstyle"> <XSL:með-Gildi nafn="CurPos" velja="$CurPosition" /> </XSL:gilda-sniðmát> </XSL:þegar> <!-- Pass núverandi stöðu og lastrow til itemstyle.xsl Grid sniðmát. ItemStyle.xsl mun nota það til að senda frá sér opna og loka <borð> merki. --> <XSL:þegar próf="@ Style = 'Tafla'"> <XSL:gilda-sniðmát velja="." ham="itemstyle"> <XSL:með-Gildi nafn="CurPos" velja="$CurPosition" /> <XSL:með-Gildi nafn="Síðast" velja="$LastRow" /> </XSL:gilda-sniðmát> </XSL:þegar> <XSL:annars> <XSL:gilda-sniðmát velja="." ham="itemstyle"> </XSL:gilda-sniðmát> </XSL:annars> </XSL:velja> </XSL:sniðmát> |
Athugasemdirnar lýsa tilgangi breytingar.
Auðvitað, the "OuterTemplate.CallItemTemplate" is itself called from another template. Locate that template by searching for this text string:
<XSL:sniðmát nafn="OuterTemplate.Body">
Fletta í gegnum leiðbeiningar á OuterTemplate.Body og settu LastRow breytu sem hér segir (sýndur sem athugasemd í skáletrun):
<XSL:kalla-sniðmát nafn="OuterTemplate.CallItemTemplate"> <XSL:með-Gildi nafn="CurPosition" velja="$CurPosition" /> <!-- Settu LastRow breytu. --> <XSL:með-Gildi nafn="LastRow" velja="$LastRow"/> </XSL:kalla-sniðmát>
Eftir allt þetta, við loksins hefur það sett upp á réttan hátt þannig að ItemStyle.xsl okkar getur gefið frá sér <borð> Tags á réttum stað.
ATHUGIÐ: Aftur, athuga í ItemStyle.xsl eftir að gera neinar breytingar þannig að þú sjá áhrif af þessum breytingum.
Við höfum tvö verkefni hér:
Fyrsta, ofarlega ItemStyle.xsl, bæta við þessa línu:
<!-- Sumir muldra tröllvaxinn sem gerir okkur kleift að sýna bandarískt. mynt. --> <XSL:aukastaf-sniði nafn="starfsfólk" stafa="D" /> <XSL:sniðmát nafn="Default" passa="*" ham="itemstyle">
Athugaðu að ég bætti það beint áður en <XSL:template name="Default" …> skýring.
Næsta, go back to our Grid template. Replace the entire Grid template with the code below. It is thoroughly commented, en ekki hika við að sendu mér tölvupóst eða leyfi athugasemdir á blogginu mínu ef þú hefur einhverjar spurningar.
<XSL:sniðmát nafn="Rist" passa="Róður[@ Style = 'Tafla']" ham="itemstyle"> <!-- ContentMain.xsl fer CurPos og síðasta. Við notum þetta til skilyrðum losa opinn og loka <borð> merki. --> <XSL:Gildi nafn="CurPos" /> <XSL:Gildi nafn="Síðast" /> <!-- Eftirfarandi breytur eru óbreytt frá venjulegu ItemStyle.xsl --> <XSL:breytu nafn="SafeImageUrl"> <XSL:kalla-sniðmát nafn="OuterTemplate.GetSafeStaticUrl"> <XSL:með-Gildi nafn="UrlColumnName" velja="'ImageUrl'"/> </XSL:kalla-sniðmát> </XSL:breytu> <XSL:breytu nafn="SafeLinkUrl"> <XSL:kalla-sniðmát nafn="OuterTemplate.GetSafeLink"> <XSL:með-Gildi nafn="UrlColumnName" velja="'LinkUrl'"/> </XSL:kalla-sniðmát> </XSL:breytu> <XSL:breytu nafn="DisplayTitle"> <XSL:kalla-sniðmát nafn="OuterTemplate.GetTitle"> <XSL:með-Gildi nafn="Titill" velja="@ Titill"/> <XSL:með-Gildi nafn="UrlColumnName" velja="'LinkUrl'"/> </XSL:kalla-sniðmát> </XSL:breytu> <XSL:breytu nafn="LinkTarget"> <XSL:ef próf="@ OpenInNewWindow = 'true'" >_blank</XSL:ef> </XSL:breytu> <!-- Hér við skilgreinum breytu, "tableStart". Þetta inniheldur HTML . Athugið að ef CurPos = 1, það felur í sér HTML í cdata tag. Annars, það mun vera tómur. Verðmæti tableStart er emited hvert skipti ItemStyle er kallað í gegnum . --> <XSL:breytu nafn="tableStart"> <XSL:ef próf="$CurPos = 1"> <![CDATA[ <Tafla border = 1> <tr bgcolor="blue"> <td><font color="white"><B>Project Name</B></letur></td> <td align="right"><font color="white"><B>Ljúka Dagsetning</B></letur></td> <td align="right"><font color="white"><B>Budget</B></letur></td> <td align="right"><font color="white"><B>Raunveruleg kostnað</B></letur></td> <td><font color="white"><B>Alls Status</B></letur></td> </tr> ]]> </XSL:ef> </XSL:breytu> <!-- Annar breytu, tableEnd skilgreinir einfaldlega borðið lokun tag. Eins og með tableStart, það er alltaf emited. Þetta er ástæða þess að gildi þess er . --> <XSL:breytu nafn="tableEnd"> <XSL:ef próf="$CurPos = $ Síðast"> <![CDATA[ </borð> ]]> </XSL:ef> </XSL:breytu> <!-- Alltaf losa innihald tableStart. Ef þetta er ekki í fyrsta , þá vitum við gildi þess . Slökkva framleiðsla sleppi því þegar tableStart ekki autt, það . Ef , it will generate stuff like "<borð>" instead of "<borð>". --> <XSL:gildi-af velja="$tableStart" disable-framleiðsla sleppi="Já"/> <tr> <!-- P:Project_x005F_x0020_Name :Project_x005F_x0020_End_x005F_x0020_Date :Project_x005F_x0020_Budget :Project_x005F_x0020_Expenses :Project_x005F_x0020_Status --> <td> <XSL:gildi-af velja="@ Project_x005F_x0020_Name"/> </td> <td align="rétt"> <XSL:gildi-af velja="@ Project_x005F_x0020_End_x005F_x0020_Date"/> </td> <td align="rétt"> <XSL:kalla-sniðmát nafn="formatcurrency"> <XSL:með-Gildi nafn="gildi" |
UPDATE (04/2008): Þessi mikli blogg sýnir góðan javascript byggir nálgun á þessu vandamáli: http://webborg.blogspot.com/2008/04/add-functions-and-events-to-sharepoint.html
UPDATE II: (04/2008): Þetta blogg útlit efnilegur og: http://www.cleverworkarounds.com/2008/03/13/free-mosswss-2007-web-part-hide-controls-via-javascript/
Nokkrum sinnum í viku, ef ekki daglega, forum users describe a requirement that would normally be met via cascading drop-downs. Til dæmis, Ég hef tvær falla niður eftirlit:
As responsible UI providers, we want it to operate like this:
There is no out-of-the-box support for this feature. Í raun, there is no OOB support for any kind of direct intra-form communication. This includes programmatically hiding/enabling/disabling fields in response to field changes elsewhere on the form.
The real objective of this article to to describe possible solutions and these are the options as I know them:
If anyone knows other and/or better options, please post a comment and I’ll update the body of this post.
<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 />
