DSXchange

I assume you need to give it a "shell" extension, not a Windows one - try .sh rather than .bat or .txt and let us know if it works more better.

XML Input? D'oh. Thought we was talking output.

Assuming that resolved your problem, please mark the post as Resolved using the big button at the top of the screen.

Boolean values don't need to be explicitly set - in essence they set themselves to true or false based on the expression. So... If IsNull(FldName_1) THEN '0' ELSE '1' Could be replaced with: Not(IsNull(FldName_1)) And then you simply reference the stage variable in the const...

In the Server plug-in, it's pretty obvious. You'll need to find that option in the PX version, something I can't help you with. Isn't there a "Help" button in the stage?

then i simply transformed the input link to output. Its not accepting the NULL (obviously) and I am getting REJECTED rows which is having NULL values. Is this approach is GOOD if the source is going to be large No, this is never a "good" approach. Use a constraint to ensure these rows never go to t...

And make sure you "Aggregate all rows".

There's a built in "routine" (for lack of a better word) that always checks imported jobs to see if they need to be "upgraded" to the latest version. I guess it would matter if you were actually importing from an older Server version - were you? If not, I'd not worry about it. Worst case, export and...

That makes no sense, but I'll take your word for it. Glad you got it sorted out, regardless.

Which is exactly what the error message told you.

Please mark the topic as Resolved using the button at the top of the screen.

Ugh. I use separate jobs for each table and run them in the proper order. Transaction Size is always 0 so there's no "inconsistent data", it is all or nothing and the jobs ensure no "exceptions" occur that we have control over.

It's an optional property of the Sequential File stage in PX to include the filename. For Server jobs, since you need to tell it the filename (typically via a job parameter) just use the parameter as the derivation of an additional field within your link.

Not sure how anyone can help without knowing what "aborts" you are getting. Please post the actual error message(s) from the job's log.