DSXchange

Ok, fair enough. You've found one specific example of an issue, which I'll leave to others to discuss should they so desire. Just seems a little disingenuous to me to classify this as "Parallel jobs can't even read in CSV files created by server jobs". [shrug]

That is how it should be working. We use Oracle and the SP stage and have never seen this. Time to check with your official Support provider, it seems.

Never seen that behaviour. What database?

Hmmm... you're always going to have problems with delimiters inside a delimited string. How well would even a Server job read this? Something to play with in my spare time, I guess.

Rather than the complex query, you could go old school and use your editor of choice to find all occurances. You need to go 'up' from each one to find the 'BEGINJOB' record so you'd know where you'd found it.

mandyli wrote:then how to include the sequence in the insert statement to generate the sequence for the first column which is the sequence generated primary key

Ray has already answered this, rather completely, specific example and all.

Grabbing tightly to the hi-jack as we veer off course... It seems odd to me that server and parallel jobs have such a hard time interacting. Parallel jobs can't even read in CSV files created by server jobs. Is this from personal experience or something you picked up from the forums? I don't "do" P...

If you are willing to share what this transform does, I'm sure people here would be willing to share a more 'PX appropriate' way to accomplish the same thing.

A real live honest to goodness Server transform? You can't. Well... unless you're willing to play the BASIC Transformer game, that is.

Read the column from the table and pass it to an XML Input stage for parsing. Mark the source column as an XML Document and supply the correct XPath expressions.

It's a plain text file that lives in each Project. Assuming everything in it should always be identical across projects, you can simply copy the file. Otherwise, you'll need to just move the relevant bits.

No worries. Thanks!

Think I'll change this to Resolved as we've successfully implemented a manual solution for this and since that seems to be The Answer... :D

Hey Ernie - just curious if you ever turned up anything on this?

No such thing. You could, however, create them in one Project and then script (or manually) handle the move of the relevant DSParams data to all other Projects.

You need to confirm that we understand your issue correctly. I'd wager you'll need to contact Support for this, though.