Hi,
I am creating a file at the end of my job. After it is created I want to send this file through e-mail. Instead of sending as attachments I want the file contents to come under my Email body. How can I do ? Please advise.
Mailing file contents
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 342
- Joined: Tue Nov 04, 2008 10:38 am
- Location: Chennai, India
-
- Premium Member
- Posts: 425
- Joined: Sat Nov 19, 2005 9:26 am
- Location: New York City
- Contact:
The body of the email notification activity don't allow parameters
But if you would like to used a server job then try below using DSSendMailTester utility:
The job design looks like this : Folder Stage --> Transformer --->Seq File
Read your file with a folder Stage, the content of the file will be in the "Record" column, in the transformer call utility DSSendMailTester( To address, From address, Subject line, Server name, Message body) as a derivation to a dummy or log column in the sequential file. Map the "Record" column to the Message body argument , rest of argument could be parameters
Let us know your results
But if you would like to used a server job then try below using DSSendMailTester utility:
The job design looks like this : Folder Stage --> Transformer --->Seq File
Read your file with a folder Stage, the content of the file will be in the "Record" column, in the transformer call utility DSSendMailTester( To address, From address, Subject line, Server name, Message body) as a derivation to a dummy or log column in the sequential file. Map the "Record" column to the Message body argument , rest of argument could be parameters
Let us know your results
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
-
- Participant
- Posts: 342
- Joined: Tue Nov 04, 2008 10:38 am
- Location: Chennai, India
Well, that's an interesting solution.
I would simply script something to run 'after job'. Or if I was going to use that routine, I would create a copy of it and name it something more appropriate: DSSendMailInline or some such. More... "future proof" that way I would think as well.
I would simply script something to run 'after job'. Or if I was going to use that routine, I would create a copy of it and name it something more appropriate: DSSendMailInline or some such. More... "future proof" that way I would think as well.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers