Subject:CSV set up to support predefined XML Author:Steve Hendricks Date:21 Jun 2012 11:22 PM
Hi,
I'm using the trial version. We're trying to bring a CSV format into a predefined XSD. I've attached it as well as the XML that was manual put together. How should I form the CSV to map to the XSD and generate the correct XML? There are repeating components and maybe subcomponents (terminology)? I've looked at the component and subcomponent delimiters but the documentation isn't very clear. Thank you for the help.
Subject:CSV set up to support predefined XML Author:Steve Hendricks Date:22 Jun 2012 09:21 AM
Hi,
That's the basis of my question. The data will come from a variety of sources however be linked at the Product level via the Style. If you use the Grid tab inside of Stylus Studio, you'll see breakdown of Product. I want to create the CSV that will map to the schema and obviously need to know how to process the CSV via a converter. I hope that answers your question. Thanks for the help.
Subject:CSV set up to support predefined XML Author:Ivan Pedruzzi Date:22 Jun 2012 01:32 PM
Ideally it would be better to go from your multiple sources to XML
but you may need the flat file for some other reasons.
The project attached is one of many ways to go.
The flat file format use the first column to specify the record type and use pipe as separator character.
Product|Drop V Neck|DOTS|This pretty v neck tank is perfect for casual wear.|Y|11767JT4348||$5.00||||||74||COLOR_NAME|SIZE_NAME|1
CategoryToProduct|1-1-1|1|Y
ProductVariant|82673302|5.00|LIME PUNCH|99|XL|353|0104|Y|Y
...
XML Converters turns it into XML
<table>
<row>
<column.0>Product</column.0>
<column.1>Drop V Neck</column.1>
<column.2>DOTS</column.2>
The XSLT transformation generates the final result and the post XML schema validation step checks the output
An alternative solution would be generating separate flat files for product, CategoryToProduct, ProductVariant, etc. and using IDs to rebuild the hierarchy in XML.
Subject:CSV set up to support predefined XML Author:Steve Hendricks Date:27 Jun 2012 10:18 AM
Hi,
Everything is going well. The templates were well defined. As a result, we'll move forward with purchasing the product. Great job on the technical support. The "other guys" were not as helpful. The only question right now is setting up the XLST functions. I've dropped in a for-each select in place but I need to create the condition for selection. Here's the before and after. I had to type in the after. Is there a graphical way to do it versus typing?
Before
<xsl:for-each select="table/row">
After
<xsl:for-each select="table/row[column.0 = 'Store']">
Subject:CSV set up to support predefined XML Author:Ivan Pedruzzi Date:27 Jun 2012 04:05 PM
Happy to hear.
Predicates are supported but they are hidden by default to avoid overloading of the graphical representation. You can turn it on under tools>options>XSLT.
In addition the mapping tool allows you to use the "if" statement inside the for-each body.
Subject:CSV set up to support predefined XML Author:Steve Hendricks Date:27 Jun 2012 11:48 PM
Hi,
Got pretty far along with creating a new XLST but got stuck with a repeating elements. I've attached the txt file, conv, xsl and xsd via a zip file. When I do the preview, it generates fine until it gets to the lower level and then it creates weirdness inside of StoreEvent. It repeats as "StoreEvents/Store/StoreEvents/StoreEvent/Title/Description"
I want it to be "StoreEvents/StoreEvent/Title/Description".
I also noticed that my root level "StoreImport" doesn't appear in the Target Document within the mapper. It shows Dots_Store_Location.xsd/Stores/.../Store/ActiveFlag. I think it should be showing Dots_Store_Location.xsd/StoreImport/Stores/.../Store/ActiveFlag
I can't relate the apply templates in the match row/column.0 = StoreEvent to Stores as it gives me an Invalid Linking Operation. Thoughts?