I want to combine few columns, like, Strre name, Ext No, Colony into one single column. I am using the transformer stage for same and
If the input fileds are:
Street
ExtNo
Colony
and the output field is : AddressLine1
then i have put AddressLine1 derivation as : Street:ExtNo:Colony
Now for most of the times ExtNo is a NULL. And because of this all the records are being dropped off. There is no output hence out of the transformer stage.
Please mention if i am missing some property in the Transformer stage
or
Mention an alternative stage to do the above task.
To combine columns in QS
Okay. In real, there are some 26 fields coming out of standardization stage which i am feeding to the Transformer. All these fields can be NULL if required. Hence, i guess i would need to put this rule to every field right?chulett wrote:I assume this will work here:
Street:NullToEmpty(ExtNo):Colony
Once you cat a null onto a string, the result is null no matter the other values, so you need to avoid doing that at all costs. ...
-
- Premium Member
- Posts: 425
- Joined: Sat Nov 19, 2005 9:26 am
- Location: New York City
- Contact:
Re: To combine columns in QS
DivStands,
The transformer stage is fine ... just handle the nulls values. In this case you should be Ok using NullToEmpty function
Street:NullToEmpty(ExtNo):Colony
The transformer stage is fine ... just handle the nulls values. In this case you should be Ok using NullToEmpty function
Street:NullToEmpty(ExtNo):Colony
divstands wrote:I want to combine few columns, like, Strre name, Ext No, Colony into one single column. I am using the transformer stage for same and
If the input fileds are:
Street
ExtNo
Colony
and the output field is : AddressLine1
then i have put AddressLine1 derivation as : Street:ExtNo:Colony
Now for most of the times ExtNo is a NULL. And because of this all the records are being dropped off. There is no output hence out of the transformer stage.
Please mention if i am missing some property in the Transformer stage
or
Mention an alternative stage to do the above task.
Julio Rodriguez
ETL Developer by choice
"Sure we have lots of reasons for being rude - But no excuses
ETL Developer by choice
"Sure we have lots of reasons for being rude - But no excuses