Ita, hoc mane,, fili mi determinatur ad visendam aetate tredecim quid 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 quis 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 🙂
Job de collegio in prima mea 1991, Felix essem, cum ad opus vestibulum 13 locus, 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.
Lorem ipsum demissi immunde volvitur nova et cooperatorem, Jeff. Our job was to power up the Unix box, fac o / S procurrentem, ERP ratio install, configurare ERP, train people on the ERP and do custom work for folks on the spot. (Hoc est somnium officium, praesertim recta de collegio). Before we could really get off the ground, opus EXPEDIO omnem viridem fistulae, put them on desks and wire them. And the best part was that we had to put the RJ11 connectors on ourselves.
Qua de causa etiam non numquam quaerere et tunc intellexerunt, nos ante aliquot contrahentium cuneus venit per funem et currere per herbam, but we didn’t have them put on the connectors. Ita, there was a "patch box" with dozens of of unlabeled cables in the "computer room" et haec snaked circa aedificium ad varia loca in ædificationibus.
Per modum operati ex decursu auctor, tentans singulis filum, induendo COPULATRIX (condita certus fuit recta nos. transgressus), impendendum in viridi aliquantulus occasus vera erant fistulae et impressoribus, 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.
Sed, 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, sed ebdomada typographum convertetur in tres-tantibus.
Si id non sciunt, aut oppresserit, de viridi et impressoribus modum fistulae, there are various options that you deal with by setting various pins. 8-frenum, 7-frenum, paritatem (etiam / impar / nullus), probably others. If you get one of those settings wrong, fistulam vel typographum adhuc ostendit effercio, sed erit summa INANIS STREPITUS, or it will be gibberish with a lot of recognizable stuff in between. Utique, these pins are hard to see and have to be set by using a small flat-edge screw driver. And they are never standard.
Nos posuit ad primum multa vigent vocat cum Guidone NJ (a colorum fortasse computatrum osor qui maledixerit nobis ad diem hanc). 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, si non vere certus bene ageret.
Vivamus tempus est ut, fremunt omnibus in Baltimore, sed potest non adepto ad operari maledixit procer in NJ! 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", sperans quod maybe erit aliquid in fila, ut purgamentum quod indicabunt nobis quid sumus malefactoribus.
Cumque venissemus in Fax, we immediately knew what was wrong. Videte, our method of testing whether we had configured a printer correctly was to issue an "lp" sicut hoc praeceptum:
LP / c / passwd
Basically, 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:
Faber:*:100:100:8LXXIV A-(muneris):/Home / fabri:/usr / bin / SH :*:200:0::/Home / hospitis:/usr/bin/sh
We had been printing out the password file over and over again for several weeks and it was printing correctly. Autem, ad finem user, it was "printing garbage".
</finem>
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. De 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).
Ita, add "compression" to the hazards list.
</finem>
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.
Autem, 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.
Primum, 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.
Secundo, there does not seem to be any mechanism to "monetize" a windows live space blog. In facto, 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.
Gratias!
<Finis />
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.
<Finis />
Missionem: In SharePoint Designer workflow, you need to determine if a date field is blank.
Forsit: 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".
Solutio: Convert the date to a string. Use string comparison to determine if the date is blank.
Collaborative offa:
The following screen shots show how to do this. In hoc missione, in agrum item, "Environmental Permits:First Permit Reminder Date", responsio subiiciatur et workflow ignes.
Notes:
Cum hoc probatum, I was pleasantly surprised to learn that it works. I was worried that SharePoint Designer might disallow the string assignment (INCERTUS:StringReminderDateDate) sed non sinunt,.
Qui etiam de me passurum, pretium fore aut irritum et flare ad WF runtime vel maybe attollere global temperatus 1/2 Gradus, sed erant illis de vano.
</finem>
Hodie, 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, you configure the CQWP to connect to its data sources, then you export it to your workstation, modify <CommonViewFields>, upload, remove the original and now it’s ‘primed’ to display those other columns. Postero, open up 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. Tandem, modify the template to render your new fields! (Don’t forget to check it back in so that other users can see the results)."
It’s all quite clear to me (and most of us SharePoint developer types) what’s going on and how it’s quite nice, vere, that the data retrieval aspects of the CQWP are so well-separate from the data presentation aspects. Sed, it’s not so easy to explain, is it?
<Finis />
Ex arca archa, MUSCUS’ Quaero Web content Parte (CQWP) ostenditque fructus ejus in elencho format, similar to search results. It is also possible to display the results in a grid format (i.e. HTML mensam format). 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, ut tituli, budget, consummatio expectatur date, remaining budget and other summary type fields. By "singleton" I mean a custom SharePoint list guaranteed to contain only one item. Simplistically, is vultus amo is:
The technical approach is much the same as described hic (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 like this generates that result:
<html> <corpus> <centrum> <mensamque border=1> <!-- Labels --> <tr bgcolor=blue> <td><font color=white><b>Project Name</b></font></td> <td align=right><font color=white><b>Complete Date</b></font></td> <td align=right><font color=white><b>Budget</b></font></td> <td align=right><font color=white><b>Actual Expense</b></font></td> <td><font color=white><b>Overall Status</b></font></td> </tr> <tr> <td>Re-wire computer room.</td> <td align=right>02/01/08</td> <td align=right>22,500.00</td> <td align=right>19,000.00</td> <td>In Progress</td> </tr> <tr> <td>Provision servers for SQL Upgrade</td> <td align=right>04/01/08</td> <td align=right>7,500.00</td> <td align=right>0.00</td> <td>Planned</td> </tr> </mensamque> </centrum> </corpus> </html> |
Follow these steps to create the grid:
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 hic (http://msdn2.microsoft.com/en-us/library/bb897399.aspx) and Heather Solomon’s blog hic (http://www.heathersolomon.com/blog/articles/CustomItemStyle.aspx).
Begin and implement steps one through five as per the MSDN documentation and Heather Solomon’s article.
Ad hoc, you’ve added your CQWP to the page and you have your <CommonViewFields> configured as necessary.
Following the usual steps, I get these intermediate results:
1. Partum a content type, a templatized custom list for that content type and two sites. Here is the content type:
Here is the site structure:
2. Add the CQWP after creating my project subsites and singleton project summary lists:
3. Add all the additional information I want via the <CommonViewFields>:
<proprietate nomen="CommonViewFields" typus="filum">Project_x0020_Name;Project_x0020_Expenses;Project_x0020_Status;Project_x0020_Start_x0020_Date;Project_x0020_End_x0020_Date;Project_x0020_Budget</proprietate>
Note that I had to keep all the property fields on one line or it would not work (CQWP would tell me that the query returned no items).
4. Ad hoc, 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 to create a customized / unghosted version of ItemStyle.xsl. I follow Heather’s advice, up through step 11 and get these intermediate results:
4.1: Name my XSL template as follows:
<p:template name="Grid" match="Row[@Style=’Grid’]" mode="itemstyle">
I also slightly modify her suggested <p:nam quisque- …> by adding a <br /> tag to provide a cleaner listing:
<p:nam quisque- elige="@*"> P:<p:valor ex- elige="nomen()" /><br/> </p:nam quisque->
4.2: I modify the web part, go to appearance and select my "Grid" style:
Apply the change and here is the result:
We can see from the above that the fields we want (Project name, expense, status, etc) 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. Verbigratia, we reference Project Status as "Project_x005F_x0020_Name".
Ad hoc, we depart from Heather’s blog and from the shoulders of these giants, I add my own little bit.
MONUMENTUM: Cum utrisque mutationibus tam ContentQueryMain.xsl ItemStyle.xsl, tu opus ad reprehendo retro in conspectu illorum lima videtis effectum mutationes tuas.
Nam eget consilium-factionis, 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 <mensamque> tag emiserit ante in primo versu de notitia et occlusio <mensamque> tag after emitting the last row. To accomplish this, ContentQueryMain.xsl is modified to pass two parameters to our "grid" luctus in ItemStyle.xsl, "last row" and "current row". ItemStyle.xsl uses these to conditionally emit the necessary tags.
Heather scriptor Salomon usura ars, we locate ContentQueryMain.xsl. It is located in the same place as ItemStyle.xsl. This screen shot should help:
His motus ad opus:
Locate the template named "OuterTemplate.CallItemTemplate" identified by the string:
<p:Template nomen="OuterTemplate.CallItemTemplate">
Replace the whole template as follows:
<p:Template nomen="OuterTemplate.CallItemTemplate"> <p:param nomen="CurPosition" /> <!-- Add the "LastRow" parameter. We only use it when the item style pass in is "Grid". --> <p:param nomen="LastRow" /> <p:elegerit> <p:cum test="@Style='NewsRollUpItem'"> <p:apply-templates elige="." mode="itemstyle"> <p:cum param- nomen="EditMode" elige="$cbq_iseditmode" /> </p:apply-templates> </p:cum> <p:cum test="@Style='NewsBigItem'"> <p:apply-templates elige="." mode="itemstyle"> <p:cum param- nomen="CurPos" elige="$CurPosition" /> </p:apply-templates> </p:cum> <p:cum test="@Style='NewsCategoryItem'"> <p:apply-templates elige="." mode="itemstyle"> <p:cum param- nomen="CurPos" elige="$CurPosition" /> </p:apply-templates> </p:cum> <!-- Pass current position and lastrow to the Grid itemstyle.xsl template. ItemStyle.xsl will use that to emit the open and closing <mensamque> tags. --> <p:cum test="@Style='Grid'"> <p:apply-templates elige="." mode="itemstyle"> <p:cum param- nomen="CurPos" elige="$CurPosition" /> <p:cum param- nomen="Last" elige="$LastRow" /> </p:apply-templates> </p:cum> <p:alioqui> <p:apply-templates elige="." mode="itemstyle"> </p:apply-templates> </p:alioqui> </p:elegerit> </p:Template> |
The comments describe the purpose of the changes.
Utique, the "OuterTemplate.CallItemTemplate" is itself called from another template. Locate that template by searching for this text string:
<p:Template nomen="OuterTemplate.Body">
Scroll through the instructions in OuterTemplate.Body and insert the LastRow parameter as follows (shown as a comment in italics):
<p:Template voca- nomen="OuterTemplate.CallItemTemplate"> <p:cum param- nomen="CurPosition" elige="$CurPosition" /> <!-- Insert the LastRow parameter. --> <p:cum param- nomen="LastRow" elige="$LastRow"/> </p:Template voca->
After all of this, we finally have things set up properly so that our ItemStyle.xsl can emit <mensamque> tags at the right place.
MONUMENTUM: Iterum, check in ItemStyle.xsl after making any changes so that you see the effect of those changes.
We have two tasks here:
Primum, near the top of ItemStyle.xsl, add this line:
<!-- Some mumbo jumbo that enables us to display U.S. currency. --> <p:decimales format- nomen="staff" digit="D" /> <p:Template nomen="Default" match="*" mode="itemstyle">
Note that I added it directly before the <p:template name="Default" …> definition.
Postero, go back to our Grid template. Replace the entire Grid template with the code below. It is thoroughly commented, but don’t hesitate to email me or leave comments on my blog if you have questions.
<p:Template nomen="Grid" match="Row[@Style='Grid']" mode="itemstyle"> <!-- ContentMain.xsl passes CurPos and Last. We use these to conditionally emit the open and closing <mensamque> tags. --> <p:param nomen="CurPos" /> <p:param nomen="Last" /> <!-- The following variables are unmodified from the standard ItemStyle.xsl --> <p:variabilis nomen="SafeImageUrl"> <p:Template voca- nomen="OuterTemplate.GetSafeStaticUrl"> <p:cum param- nomen="UrlColumnName" elige="'ImageUrl'"/> </p:Template voca-> </p:variabilis> <p:variabilis nomen="SafeLinkUrl"> <p:Template voca- nomen="OuterTemplate.GetSafeLink"> <p:cum param- nomen="UrlColumnName" elige="'LinkUrl'"/> </p:Template voca-> </p:variabilis> <p:variabilis nomen="DisplayTitle"> <p:Template voca- nomen="OuterTemplate.GetTitle"> <p:cum param- nomen="Title" elige="@Title"/> <p:cum param- nomen="UrlColumnName" elige="'LinkUrl'"/> </p:Template voca-> </p:variabilis> <p:variabilis nomen="LinkTarget"> <p:si test="@OpenInNewWindow = 'True'" >_blank</p:si> </p:variabilis> <!-- Here we define a variable, "tableStart". This contains the HTML that we use to define the opening of the table as well as the column labels. Note that if CurPos = 1, it includes the HTML in a CDATA tag. Otherwise, it will be empty. The value of tableStart is emited every time ItemStyle is called via ContentQueryMain.xsl. --> <p:variabilis nomen="tableStart"> <p:si test="$CurPos = 1"> <![CDATA[ <table border=1> <tr bgcolor="blue"> <td><font color="white"><b>Project Name</b></font></td> <td align="right"><font color="white"><b>Complete Date</b></font></td> <td align="right"><font color="white"><b>Budget</b></font></td> <td align="right"><font color="white"><b>Actual Expense</b></font></td> <td><font color="white"><b>Overall Status</b></font></td> </tr> ]]> </p:si> </p:variabilis> <!-- Another variable, tableEnd simply defines the closing table tag. As with tableStart, it's always emited. This is why its value is assigned conditionally based upon whether we've been passed the last row by ContentQueryMain.xsl. --> <p:variabilis nomen="tableEnd"> <p:si test="$CurPos = $Last"> <![CDATA[ </mensamque> ]]> </p:si> </p:variabilis> <!-- Always emit the contents of tableStart. If this is not the first row passed to us by ContentQueryMain.xsl, then we know its value will be blank. Disable output escaping because when tableStart it not blank, it includes actual HTML that we want to be rendered by the browser. If we don't tell the XSL parser to disable output escaping, it will generate stuff like "<mensamque>" instead of "<mensamque>". --> <p:valor ex- elige="$tableStart" disable-output-erepta="Imo"/> <tr> <!-- P:Project_x005F_x0020_Name P:Project_x005F_x0020_End_x005F_x0020_Date P:Project_x005F_x0020_Budget P:Project_x005F_x0020_Expenses P:Project_x005F_x0020_Status --> <td> <p:valor ex- elige="@Project_x005F_x0020_Name"/> </td> <td align="ius"> <p:valor ex- elige="@Project_x005F_x0020_End_x005F_x0020_Date"/> </td> <td align="ius"> <p:Template voca- nomen="formatcurrency"> <p:cum param- nomen="valor" |
UPDATE (04/2008): Magnum hoc blog introitu ostendit a bono javascript dicentur aditus ad hoc problema: http://webborg.blogspot.com/2008/04/add-functions-and-events-to-sharepoint.html
UPDATE II: (04/2008): Hoc blog introitu spectat tam promittens: http://www.cleverworkarounds.com/2008/03/13/free-mosswss-2007-web-part-hide-controls-via-javascript/
Plures temporibus a septimana, si minus quotidie,, forum users describe a requirement that would normally be met via cascading drop-downs. Verbigratia, Habeo duas occumbo-down imperium:
Author UI ut suggero, sic operari volumus:
There is no out-of-the-box support for this feature. In facto, 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.
Hic articulus ad describeret obiectiva rerum solutionum possibilis, et haec sunt bene ut ego cognosco eas,:
Si quis scit et / vel potius bene, Vestibulum eget velit et corpus, consectetur adipiscing elit felis.
<Finis />
To filter for a query for the Yes/No check box entitled "PG Milestone", configurare haec CQWP:
Hoc est aliud unum ex his patet, quondam vos scire, sed difficile invenies-ad-modum-responsum ad quaestiones:: Ita quam ad spurcamen in / box nullo morante usura query telam contentus parte.
Prima quaero praecessi I find using the search term "filter yes/no content query web part" planae de iniuriam est, Lorem ita ego eum hoc loco potest, si recte et ex dine Search Results.
Suus facile: True values = "1" and false values do not equal "1" (pulchellus RED, ultro).
In superiore exemplo, I created site column of type "Yes/No (checkbox)" named "PG Milestone". I added it to a doc library, Lorem paucis documentis, posuit et valorem copulabis expertus.
<Finis />
