Journaling HTML messages
Posted: Thu Oct 15, 2009 6:26 pm
I have set the Journaling feature to create a new record in my existing Communication History table in my solution. The problem is that the value in the $note variable is not evaluating properly if the message was HTML.
The final value set into my field literally ends up looking like this (including double quotes and pilcrows):
"From: Hedrich Michaelsen <[email protected]>¶To: Hedrich Michaelsen <[email protected]>¶Cc: ¶Bcc: ¶Subject: October Postcard¶¶This message is best viewd in HTML.¶¶HTML PART FOLLOWS:¶<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\">¶
This is what goes into the $note variable and subsequently into my message field. It drops a fair amount of what is in the _JournalEntry field in the fmSpark Message table. When it gets to the final script that should evaluate $note if it is enclosed in quotes, that fails because the portion of the text that ends up in $note has lost the final double-quote character. Any clues as to what is going on here? I did make some small and careful modifications to the journaling script to capture a pipe-separated list of enclosures but I don't think this is causing the problem.
The final value set into my field literally ends up looking like this (including double quotes and pilcrows):
"From: Hedrich Michaelsen <[email protected]>¶To: Hedrich Michaelsen <[email protected]>¶Cc: ¶Bcc: ¶Subject: October Postcard¶¶This message is best viewd in HTML.¶¶HTML PART FOLLOWS:¶<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\">¶
This is what goes into the $note variable and subsequently into my message field. It drops a fair amount of what is in the _JournalEntry field in the fmSpark Message table. When it gets to the final script that should evaluate $note if it is enclosed in quotes, that fails because the portion of the text that ends up in $note has lost the final double-quote character. Any clues as to what is going on here? I did make some small and careful modifications to the journaling script to capture a pipe-separated list of enclosures but I don't think this is causing the problem.