<b:AriadneNormalized>
<b:AddressEntries>
{
for $AddressEntry in /a:AriadneRaw/a:AddressEntries/a:AddressEntry
return
<b:AddressEntry>
<b:Division>
{
$AddressEntry/a:DIV/text()
}
</b:Division>
etc...
I can see the default scenario has an main input file identified, which is an XML file dumped out by a flat file converter. I would like to create a pipeline like in this video: http://www.stylusstudio.com/videos/pipeline2/pipeline2.html so that I can use the ConvertToXML and pass the output to the XQuery.
How do I modify my xquery so that it accepts an input from ConvertToXML and still works in the mapper?
In this image, for example, I specify the flat file on the input of 'FF to XML', however the 'Normalize Raw Data' doesn't do anything as if no data came from 'FF to XML'.
Subject:Using adapter URL in pipeline. Author:Ivan Pedruzzi Date:11 Jun 2013 04:02 PM
if you are not getting anything most likely you converter block is not configured correctly, check the converter URL also what kind of flat file are you converting?
If you are still in trouble, zip your project with all your files and send it to
stylussupport@ivitechnologies.com
Subject:Using adapter URL in pipeline. Author:chris misztur Date:11 Jun 2013 04:07 PM
The converter run on its own works fine.
It's when running it in the pipeline is when it outputs the below, instead of the converted file. Do I need to modify the xquery following the ConvertToXML to accept an adapter URL?
But I am not sure what else I need to change in the xquery FWLOR to iterate the parameter value instead of the document assigned in the mapper. It would be nice if the two were interchangable so the visual mapper remains functional but the xquery can be automated in a pipeline.