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.

It's a huge string with all the html in it?

Hi, Every recipient gets a copy of all cards (cross)? Every recipient gets one of the available cards (left join on line number)?Neither join would require java, but for 1:n a pivot does have to be applied (n has to be specified). Thanks,-Jon

Hi, Use an @include directive for the file:<%@ include file='file:///tmp/abcMeta.html' %> If your url's are in a loop or similar, unroll it so the parser can see, with the protocol outside the js:<% var urls = [['aol.com', 'AOL']]; %><% if (urls[0]) %><a href="https://<%= urls[0][0] %>"><%= urls[0][...