DSXchange

Pretty much exactly what it sounds like it would do - validate the XML against the xsd and can raise errors in the job if any of the checks fail.

Do you mean the xslt? Or the XPath Expressions generated from the xsd?

Unless the substring operators work differently in PX from Server, using input[1] would take the last character, not the first. You'd have to specify input[1,1] to get the first.

One way - get the decimal value of the upper-cased first character and ensure it falls between either 48-57 or 65-90.

So, it worked more better when you used the actual syntax I posted I see. :wink: It's been explained here quite a number of times already. Best thing I can tell you to do is search for the error message that usually starts this conversation and you'll find plenty of examples. Do an exact search for ...

I only say that because the people that know that product only seem to hang out there, so you need to post it there if you want them to see it.

You need to remove the Field Mark(s) that they return with:

Convert(@FM,"",custom EX_SH_test.$CommandOutput) <> 1

If your job type is indeed a "TX" job then you should be posting your question in the TX specific forum.

Index() and Field() would be the two primary weapons of choice.

You need to check on the physical disk space for scratch on that node, not anything with ulimit at this point.

Your log is corrupted due to too many messages being logged and the size exceeding 2GB. An exact search for "Computed blink of" should turn up many conversations on the topic as well as your options.

Field function. The last three bits should be ",",1,1 for the first field, ",",2,1 for the second field, etc. In other words: comma separated, field #, # of contiguous fields to extract.

Yes, sometimes Microsoft does give stuff away for free.

What versions does your documentation say are supported in that release?

The last value will be the max value... so, an Aggregator set to Last or Max would be one solution.

Then you need to not send them to the target, and that would typically mean a lookup against the target and only pass the records that 'fail'. Assuming your duplicates are not in your load data, that is.