I have too many elements in the input schema and want to use the inline XSLT
in Script functoid. Can I pass the whole node as an input to my inline XSLT
instead of passing each element as parameter?

Any response/samples is appreciated.

Thanks,
Balaji

[ Post a follow-up to this message ]

> I have too many elements in the input schema and want to use the inline
XSLT
> in Script functoid. Can I pass the whole node as an input to my inline
XSLT
> instead of passing each element as parameter?
>
> Any response/samples is appreciated.

If you want to handle the entire document in the XSLT functoid, you'd use
the "Custom XSL Path" property where you can specify an entire XSL
stylesheet that will be used for your mapping.  If you specify such a file,
the entire mapping content (functoids, mapping lines,...) will be ignored...

greetz

[ Post a follow-up to this message ]

What about includes ?
I cannot use xsl:include of stylesheets that contain enterprise wide generic
XSL templates (for formatting PO numbers, etc ..)
Why was is permitted in BTS200 and BTS2002 but NOT in BTS2004 :-( ???

... are there any workarounds for this ?

"Sam Vanhoutte" <sam.vanhoutte@unilin.com> wrote in message
news:eemekRWbEHA.716@TK2MSFTNGP11.phx.gbl... 
> XSLT 
> XSLT 
>
> If you want to handle the entire document in the XSLT functoid, you'd use
> the "Custom XSL Path" property where you can specify an entire XSL
> stylesheet that will be used for your mapping.  If you specify such a
file,
> the entire mapping content (functoids, mapping lines,...) will be
ignored...
>
> greetz
>
>

[ Post a follow-up to this message ]