Hello,The solution worked in the end when I changed the routing from mid-sorce instance to internal email delivery. A couple of things were not so clear in the explanation:The extraction activity should have this format on the naming convention of the file:  <%= vars.filename %>yourfilename.csv and ...

Hello @Raaghuik and @Jean-Serge_Biro ,I am using the same approach as above but I always have the same issue related to the mid-source instance.Can you please advice on what the issue is?Thanks a lot,

Hey @SushantTrimukheD and @ParthaSarathy ,Thanks a lot for your feedback.I tried the above but I still have the same issue.DLV-490089 The upload of the attachments to the mid-sourcing server has failed. What am I doing wrong?Thanks,

Hello Everyone, Do you know how to attach a CSV file calculated on the workflow to an email or alert activity?I have tried an approach that was suggested here via attachments on the delivery but I have the bellow error.I really appreciate any help you can provide.

Hello, This approach is not working as Adobe gives the below error. 

Hello,Do you have any updates here?I tried the solution with the email delivery but then I had this error.There is nowhere in the explanation that you need to upload the file somewhere else or any step related to that. 

Hello Milan,Thank for that but i have seen that solution also and is not helping on my case.I am looking for a mass update of the Delivery and tracking logs not just for 1 recipient that I may know but at multiple recipients at the time base on the same email.I think that this is possible with the u...

Does anyone knows how the Update and merge collections works? I have the same issue. Thanks

Hello All, I would like to see an example of merging duplicate recipients to a specified winner and together to merge also the Delivery logs.I want all the Delivery logs to be transferred to the winning recipient.I know that is the option Updating and merging inside the Update Data activity but I do...

the code doesnt work if i put in a java script activity after the continuous delivery: delivery.operation_id = instance.operation_id;