Comments on: SharePoint: Extending the DVWP – Part 9: Oops! Failed Setting Processor Stylesheet

By: Jim Bob Howard

Jim Bob Howard — Thu, 23 Sep 2010 20:28:02 +0000

Nice! Glad this helped.

Blessings,
Jim Bob

By: Richard

Richard — Thu, 23 Sep 2010 20:27:00 +0000

Hello Jim,

I had an issue with SPD 2010 and form action workflows that is now resolved. SPD 2010 adds a $Pos variable and value to the dvt_1.automode template when you try to create a form action workflow. It doesn’t help. It needs to be deleted, and the instructions that you provided here need to be followed instead. The workflow will then work! Thanks.

By: Jim Bob Howard

Jim Bob Howard — Mon, 09 Aug 2010 12:20:51 +0000

Dear Greg,

No, it actually comes out with the ‘_’ in that one. Go figure. ;)

Blessings,
Jim Bob

By: Greg

Greg — Sun, 08 Aug 2010 00:18:12 +0000

Jim,
Indeed advanced XSL but as you mentioned, Marc’s series and eBook is going to help with calling templates ‘with’ parameters and making sure on the other side, the template is ready to receive the parameter (using ).

Since the Pos parameter is defined as

I think you may have a typo at the end of your precedent article when it reads:
From a human readability standpoint, it would come out to ff1{_$Pos} but that doesn’t really help it be more readable.)

It should read ‘come out to ff1{$Pos}’ right? ;-)

Quite clever to figure out how to resolve the error thrown by SPD. Makes a lot of sense after the facts but nice debugging!

Greg