DSXchange

Hard to say. You are on 8.0? Unfortunately Tracing doesn't work there (you can try it, by usng the Trace tab at the Job Run Dialog....select your WSTransformer on the left, and then check all of the boxes on the right). If it's working, you will see a giant set of traces in the DS Log, with the actu...

Frustration often gets in the way of these things. We've all been there. I'm playing with some smart phone development on the side and know exactly what you are going thru. I nearly threw my machine across the room the other day before learning another deep behavior about java that I had never exper...

On this one, I tend to agree with Michael. There could be 1000 variables that affect something like this, not all of them on the Information Server side of things. Best to find a cool way that nails it and works in 99.99% of all situations.

As noted above, 8.0 with XML was in disarray. There were many patches. The {0} symptom is a classic. Search the forum...entries of a few years ago often mentioned this {0} thing. Call support. Clarify it and patch it. It's very likely that this is your problem, and they are the experts on how best t...

Find the full zip file for XML best practices. Do the exercises. Spend time with them. You will learn how it is done. I've pointed you to the section and the page number where this is illustrated. There isn't much more I can suggest.

No idea. Bummer. You may have to resort to something else, like trying an update to that server, or a custom sql that issues a command that will provide at least some kind of return code.....of course, checking that return code could be difficult (this would be much simpler in Server).

Ernie

in my copy of the document, it's on page 38.....the "text()" is placed after the high level "container" element of the repeating unit after performing the lookup to get the chunk.... You should have data element of XML to prevent further escaping to occur on your recently built c...

No....look more closely, especially at the section that talks about building XML documents with multiple nodes...the whole technique is based on this premise....you build a chunk then include it later in a final XMLOutput Stage....the chunk gets the XML data element and the xpath positions it....it'...

Start comparing it carefully to your other Job....how do you read that xml from disk? That one works, right? Make this second job the same. You now have the same thing, and for a simple test, you ought to have just one single column on the output, such as HCID, with a Description attribute of /Produ...

nani....set your Seq stage in Job1 so that it has NONE as the delimiter and NONE as the quote character. pillip....probably makes sense to start another thread, but find the xml best practices document elsewhere in the forum, at kim duke's site....it has lots of info on using xmloutput and the xml d...

First tell me if you can open your resulting flat file in IE? or at the very least, in Notepad....does it look like nice clean XML?

I'm not quite sure where else to point you. The answers are all in the threads above. Let's look at your string more closely: <?xml version="1.0"?> <CompressableData> <PMxml><ProductsAndRelations xmlns="http://tempuri.org/ProductsAndRelations.xsd"> <Cart HC_ID="-9" PKG_...

? Don't introduce extra complexity. Treat this as a normal process. You have a file that you received from the output of the first Job. Is it xml? Can you open it in IE? Now, import the metadata for it. Perfectly usual process. Save some table definitions for it. ....etc. Don't use custom stylesheet...

So now, write a separate second job that reads your file from the first Job (use a Server Job for testing and use a Folder Stage), and passes it to an XMLInput and parses it. Get that working perfectly before you try to put the two xmlInput Stages together.

Ernie

My memory isn't that good. There were many patches, as the old threads will attest. But now that we're far beyond fix pack one, your best bet, imho, is to discuss this with support.