Hi, Repeat insert statements for each of your cols:insert into new_eav_table (ID, AttributeName, AttributeValue)select ID, 'FirstName', FirstName from old_tableinsert into new_eav_table (ID, AttributeName, AttributeValue)select ID, 'LastName', LastName from old_tableinsert into new_eav_table (ID, At...

Hi, Sinch isn't an ootb sms connector. Are you using Generic SMPP?The default encoding for Generic SMPP connector is GSM 7, which could be 240 in DCS?It can be changed in the external account settings, maybe try UCS2. Thanks,-Jon

Could also be personalization in the delivery creating an unexpected join. Tracing the db queries is an easy way of just seeing what's happening, if you have the access.

Hi, Use an enrichment for the join instead of intersection. Thanks,-Jon

Oh it is a cross-join, numbers seemed too close for that. Wait how are the numbers stored? Mobile is a field in recipient not a relation?

Hi, Recipients exist as duplicates in recipient table for each of their phones?NB not cross join- recipients exist on left side for the numbers. Thanks,-Jon

Hi, Follow these steps:Update workflows set @campaign-id = -{campaign-id} where @campaign-id = {campaign-id} (set the negative bit for campaign-id)Export campaignFor each workflow in @campaign-id = -{campaign-id}:ExportSet @campaign-id to {campaign-id} Thanks,-Jon

Hi, Add _type="optout" to your opt-out links. Thanks,-Jon

The way tracking works is if you want to use the ootb system, the content parser which populates nms:trackingUrl and the tracking metadata xml files has to be able to parse the urls, specifically the static text '<a href="protocol://'. OOTB solutions will be constrained to that, such as the unroll a...

That's not going to work.