db4breakfast (3/12/2013)

+2 😎

I agree. So what I learned from this...

Replace ',' by ';'

Wrap

myHtmlMessage.Attachments.Add(New Attachment(Dts.Variables("Attachments").Value.ToString))

with an if statement to check if Dts.Variables("Attachments").Value has contents; something along the lines of:

if not isNull(Dts.Variables("Attachments").Value.ToString)

myHtmlMessage.Attachments.Add(New Attachment(Dts.Variables("Attachments").Value.ToString))

(I can script in other languages, not that fluent...

Hello,

I'd say that the simplest way to handle this would be to add a script task before the "OLE DB Source Editor" and assemble the SQL command there.

Regards,

PMWar

Some options:

- create a "fake" employee for external partners

- create one "fake" employee for each external partner

- assuming the employee here is a salesperson, create a SellerEntity dimension, grouping employees...

Unknown, Not Applicable, ...

I think these allow you more control over the design and data loading.

Given the use case ("amount of purchases last 12 Month"), I'd consider unlikely a user query like "amount of purchases last 12 Month" = 37, so the suggestion of categories...