Forum Discussion
Spooky, that sample works for me too it is just a redacted/cut down representation of the larger original. Maybe there were some newlines or tabs that were purged via cut/paste… Cant see anything invalid in the original, that still shows the “mixed content is not supported” error…
Had a closer look, in the original machine-generated xml the elements were indented with some kind of space characters and the parser failed. Changing these to tab characters and the parser worked fine… Just a bit confusing as the failing XML appears to be valid UTF-8 XML.
Thanks anyway,
Mike
PIMData.txt (1.8 KB)
hi @bojanvelevski i was trying to frame that structure will share the sample input and xsd pls could u help pls
samplerecords.json (262 Bytes)
Please convert PIMData.txt to PIMData.xsd as the template is in that format
Please also find output expected xml in txt format
outputxml.txt (3.2 KB)Hi rashmi,
Good day, instead of using an xml generator snap have you tried the xml formatter? I don’t know if this is your required output but xml formatter accepts an outgoing format as XSD
XML output using PIMData.xsd
Updates:
,
I’m not that familliar with XSD so I manipulate the sample input using a mapper snap, attached poc pipeline
canvas 15_2022_12_03.slp (16.8 KB)
Thanks,
EmEm
Related Content
- 3 years ago