MUSCUS michi “Obvius negavit,” ad creare a workflow Negotium, Sed ego vere praesto

2 Restituo

I’ve implemented a workflow using SharePoint Designer in a site which is mainly read-only to "NT_AUTHORITY\Authenticated Users" (i.e. omnes). There is a forms library for an InfoPath form. There is an associated workflow tasks list as well so that when the workflow operates, potest assignari munia ad populum.

Ego conteram permissione formae bibliotheca et negotium album, ut omnem creare potest formas et authenticitatis user update eorum assignari munia.

I test with my low-privileges test account.

Nisi et sem risus forma possum? –> MAXIME

Ego potest obvius munus ab pagina electronica? –> MAXIME

Video Edit workflow est opus nectunt –> MAXIME

Ego potest click in link? –> IMO … Licentiam denegari.

Recensere video cur pagina negaverit me licentiam cum eo clicca? That’s not how it’s supposed to work…

Vadam ad securitatem iterum configuration, very closely. I do it again. Existimo deleting is stipes satis patet, quia nescitis quicquam.

Tandem, I search the Internets. I find this highly unlikely MSDN forum thread: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1838253&SiteID=17

Posters videretur innuunt, quod in simplici actu exporting workflow est ad coegi disco firmabo MUSCUS securitas a fluxi? I can hardly believe I just typed that. I’m reminded of the South Park episode about the 9/11 Stan est coniuratio ubi petens nostrum Preznit, "Really?" over and over again.

Ita, nihil perdere, Ego ignis sursum SPD, vox-click in workflow, et salvabo eam meam c:\ drive. That would be the c:\ drive on my laptop. I’m looking over my shoulder the whole time so that no one will ask me, "why are you saving that workflow to your laptop?"

INCREDIBILITER, that solves my problem. I can edit the task.

Ex hoc ego nominare hoc esse maxime prodigiosum workflow de Workaround 2007.

</finem>

Technorati Tags:

SharePoint amet, Item scriptor current “Absoluta encoded URL” et https

4 Restituo

We often want to send an email that includes a hyperlink to the item or document that triggered the workflow. We can use current item’s "Encoded Absolute URL" for this purpose. Autem, it always seems to use "http" for the URL protocol. If your site runs on HTTPS then it will not work for you.

imaginem

Fuit quantum ego scient, there is no out of the box solution to this problem. If you need to use HTTPS, you have no out of the box option.

To solve it, create a custom action that provides a string replace function to use in your workflow. Alternatively, use a 3rd party tool such as the excellent package here: http://www.codeplex.com/spdwfextensions 🙂

</finem>

Technorati Tags: ,

Vivos et Securus: Determine Internal Column Name of a Site Column

3 Restituo

UPDATE: Jeremy Thake has blogged about this and put up some code for a console application that shows internal names.

I was trying to get a content query web part to display a due date from a task and because the screen label is "Due Date", I assumed that the column name to use in <CommonViewFields> is "Due_x0020_Date".

Iniuriam!

The real column name in this case was "DueDate".

How did I find it? I re-read Heather Solomon’s blog entry on modifying CQWP to show additional columns of data. She describes this process at step #13. Trust it. It’s correct. At least, it was correct for me. I did not trust it at first for another column with a much longer name.

I say "Trust it" because I did not trust it and probably wasted near two hours butting my head up against a wall. After I resolved the "DueDate" nomen, I wanted to add another field to <CommonViewFields>. Using the Solomon technique, I was getting a column name like "XYZ_x0020_Project_x0020_Due_x00".

I thought to myself, that’s clearly a truncated name. I went ahead and un-truncated it with no success. I finally used the seemingly truncated name and it worked.

Bonus tip: When I was working with the CQWP, if I added a bad internal name to <CommonViewFields>, the CQWP would tell me that the query had returned no results. Sed, if I added a data type to the field name, it would return a result. Adding the data type actually masked a problem since I was referencing a non-existent field. I could add it, but when I tried to display its value, I would always get a blank.

This did not mask the error:

<CommonViewFields>Due_x0020_Date;</CommonViewfields>

This did mask the error:

<CommonViewFields>Due_x0020_Date,DateTime;</CommonViewfields>

</finem>

Beware Breaking Changes to ItemStyle.xsl

Aliquam responsum

I was working with ItemStyle.xsl to customize the look of a Content Query Web Part and right about lunch time, I made a breaking change to the xsl. I didn’t realize it, but this had far reaching effects throughout the site collection. I went off to lunch and upon my return, noticed this message appearing in a bunch of places:

Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Windows SharePoint Services-compatible HTML editor such as Microsoft Office SharePoint Designer. If the problem persists, contact your Web server administrator.

I blamed the client (not realizing as yet that it was my fault at this point) but eventually noticed that visual studio intellisense was warning me that I had malformed XSL. I corrected it and everything started working.

Be darned careful when working with ItemStyle.xsl (and any of the global XSL files) — breaking them affects many artifacts in the site collection.

<Finis />

Filius meus laceratus Gamespot

1 Respondere

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 🙂

Dominica Funny: “Purgamentum suus Printing”

1 Respondere

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>

Aliud Network Credentials Multi-Solutio quaestionis et provocare

Aliquam responsum

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

Technorati Tags: ,

Thinking About Changing Blogging Platform

7 Restituo

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 />

Technorati Tags:

SharePoint Designer Aliquam Mittit ???? in email

1 Respondere

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 />

Technorati Tags:

Compare / Test Blank Dates in SharePoint Designer workflow

5 Restituo

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.

imaginem

imaginem

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>

Technorati Tags: