Sorry wf not available externally. Here's more detail though:
When the dynamic string is built - this is the code:
{WorkflowVariable:numLine}. Title:{WorkflowVariable:txtRiskTitle} Identified:{WorkflowVariable:txtRiskIDDate} Owner:{WorkflowVariable:txtRiskOwner} Rating:{WorkflowVariable:txtRiskRating}{Common:NewLine}
And the variable that's dropped into is txtStringCombo. I log that to the History List, and this is what is logged. It's the value of the variable on the last cycle (loop 3 - there are only 3 matches):
3. Title:#130 test Identified:12/16/2011 Owner:ENT\c617372 Rating:High
Here you can see that the line number has been incremented to 3. the data collected appears, and there is no leading semicolon. Each iteration is appended to the collection ColStrings. It is here, in ColStrings that the extra semicolons appear:
ColStrings: 1. Title:#109 This is a test of the title Identified:11/17/2011 Owner:ENT\c617372 Rating: ;2. Title:#110 This is a test of the title Identified:11/17/2011 Owner:ENT\c617372 Rating:Low ;3. Title:#130 test Identified:12/16/2011 Owner:E
Notice how there is a semicolon before the 2. and again before the 3. So as each string is assembled, the semicolon separates. When that ColStrings is used in the email, these semicolons appear.
TxtStringCombo does NOT have the semicolons, and an "Add" Collection Operation adds this to ColStrings. It is here that the ; is added - and I get that a collection must have a separator. Should I go about this in some other way perhaps?
My end goal is to get the results of a query (multiple records) to print as multiple lines in an email. I don't want to send someone 25 emails to show them the 25 records they need to look at. I need to send them 1 email with the 25 records described within.
Thanks