DSXchange

Not xmeta. The user is xmetasr, owner of the staging repository. This is new functionality in version 8.7.

You could specify unsigned integer in CL_ID, and incur a metadata mismatch instead. Better, of course, is to use an explicit conversion function. Worst case demote the warning using a message handler.

Use a BASIC Transformer stage and the Fmt() or Fold() function. Then convert the created delimiter character (@TM or @FM respectively) into "-" using Convert() function.

They are producing a patch. Stay tuned and I'll post the patch number once it's received.

Level 88 is working storage. It should not be exposed to ETL tools or, if it is, it should be ignored by them.

SCD stage supports only Type 1 and Type 2 (and "Type 1 and a half" if you follow that nomenclature). It's probably because there's yet to be industry agreement on what Type 3 and Type 4 actually mean that support for these is not provided in the SCD stage.

Don't "push", particularly on weekends!

qt_ky wrote:What is an "FME process?"

A task performed by a subject matter expert wearing a mouthguard.

Uninstall, re-install and enforce standards after that.

Time poor, plus anything I write belongs to my employer, so there's no financial incentive either.

Ah, yes, missed that one because it's something I never do. I always use specific Sort stages (even - or particularly - if they specify "don't sort - already sorted") on inputs to Sort stages.

Your assertion that Join stage waits for all records to be in is incorrect unless there is only a single key value on the input. Join reads all rows with the next value from its left input. It then reads all/any rows with that value from its right input. This is efficiently done because the inputs a...

Capture failed lookups using the Failed Lookup rule; direct these to a rejects file from the Lookup stage. Successful lookups can be directed to a Copy stage with no output if you prefer to discard these.

Specify correct port numbers on the -domain and -server options.