DSXchange

Congratulations! You found a bug in the documentation! You cannot use NullToZero in a modify stage. This function only exists in a Transformer. Yes, they give this specific example in the documentation and Yes, it is wrong. The syntax for modify would be: fieldname = handle_null(fieldname, 0) Hope t...

Well, You _can_ use a Transformer and IsNull() in a parallel job. But if You just want to do the NULL handling, it might not be the preferred way to do in PX. Like I said above: modify and handle_null() does the trick. Regards, Chris That is a server-job answer to a parallel-job question in the para...

Hi, if I remember correctly, the columns that You generate (i.e. the result of an AVG() or MAX() within the Aggregator) are always generated nullable. Your only option AFAIK would be to declare them nullable at the output of the aggregator and use a subsequent modify stage with an handle_null() oper...

Hi, if Your data always looks like "1232123 ABZC" then You can also try the ColumnImport Stage. There You can specify an input column that will be split into output columns. Much like reading from a sequential file. In Your case specify "whitespace" as separator, define an intege...

Hi all,

actually for the modify Operator/Stage You can supress warnings. Just add another "Specification=nowarn" to the stage. That should supress warnings. However, one would have to look in the "Orchestrate OEM Docs" to find this option...

Regards,
Chris

See my comments [cb] Hi I am working on DS EE 7.1 version. I have developed a job which retrieves data from sources and does a change data capture with another table find the records that have been inserted/updated or deleted. The job runs with a few warnings but no errors. They are listed as per st...