Support Article
Write email campaign output to database table in CMD
SA-41334
Summary
The user requirement is to have the final email delivery content along with email campaign output (in the form of table in database) without using default Chordiant Marketing Director (CMD) Email Delivery Engine which is part of the default product design.
Additional requirement is to increase default Extract Template (ET) text field size of 200 to a value higher.
Error Messages
Not applicable
Steps to Reproduce
Use the delivery method option as 'database' for the Delivery Channel used in the email campaign.
Root Cause
Not Applicable
Resolution
A feasible workaround for the first requirement is to have HTML content split into multiple rows in Constructed Field, which has a default text field length of 200 and would be concatenated as one in the output, and placing this Constructed Field in the ET.
Additionally, the requirement to increase default ET text field size cannot be considered as an Enhancement Request (ER) due to the following reasons:
- Placing the entire content of an email in a column of an extract template is not a feasible solution as emails can be of varying length and may further grow in size. Also, databases have strong restrictions on lengths of columns.
- The capability in the product is to produce a file or database with the personalization content and not the final delivery content. The final delivered content is the job of the delivery engine (email delivery, which the user does not want to use). Email delivery systems will follow this pattern of getting a file with personalization data and the content and merge at delivery time.
Published November 8, 2017 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.