DSXchange

The reason probably for that is because we are adding 1 to the column (recordcounter+1) therefore from source by chance if we get a value such as "1234567ABC" we want to handle such kind of scenarios.. DIGITS("1234567ABC"+1) = 1234568ABC Errr... no: DIGITS("1234567ABC"...

Basic stuff first - is this the first time you're compiling a job with a transformer or you normally can but have a problem with this one in particular?

Interesting. Let us know what they say, please.

Daren, please start your own post for this and let us know all of the gory details of the problem that you are having there.

OK... have you reported this to your official support provider?

... and is pretty slick, to boot.

I believe it is in all but I never saw 8.0, went straight to 8.1 instead. And no, Clearcase is versioning and unrelated.

What 8.x version do you have? I vaguely recall some kind of 'Super Operator' role that may do what you need but that may be an 8.1 thing. Or a figment of my imagination.

... and your target, Lnk1.VEND_NUM, is what data type? Guessing... not a string.

You can't put a "parameter in a parameter", there's only one level of resolution for them.

Or perhaps you could post the syntax you are using and what error it is throwing.

There is... when you upgrade to the 8.x release.

Gory details for those kinds of errors can only really be tracked down by the vendor, meaning you'd need to involve your official support provider for that. It could be something about the number of columns or the average record length combined with the array size setting and your specific version o...

I don't know how well that function works in a PX job, my direct experience is all in Server where the 'stage' you interrogate is always an active stage, thus typically a Transformer, or things may not go well. Not sure how that all works out in PX, what stage are you pointing it at?

Funny but... this is it.