Creating a calculated attachment where File name is computed at the time of delivery for each recipient (it can depend on the recipient) | Community
Skip to main content
R
ramakatt
Employee
July 8, 2017
Solved

Creating a calculated attachment where File name is computed at the time of delivery for each recipient (it can depend on the recipient)

  • July 8, 2017
  • 23 replies
  • 15697 views

Hi,

We are trying to attach a pdf file (from the folder placed on C:// drive for testing because, FTP is not supported) during the email delivery in the template.

  1. Specified the label  to apply to the attachment.
  2. Specified the access path of the file and its personalized name in the definition window (based on the customer name, it picks the respective file to attach).
  3. Uploaded the file to server from local drive in a different workflow as this is a mandatory step.

s_ncs_user_wizard_email_calc_attachement_010.png

I got an error below.

Questions:

1. How to resolve this issue?

2. Post the testing of attaching the files from desktop, i would like to do the same from an FTP location. How can i do this (any SFTP/other server location Adobe provides from where i can attach the files)?

PS: We have a hosted version of Adobe Campaign v6.1

Thanks,

Rajesh

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Adhiyan

    Hello Rajesh,

    This is a known limitation when using calculated attachments uploaded from the local system . The reason is that when the attachment is prepared during delivery analysis , the MTA is responsible for preparing the attachment. The MTA for a hosted environment runs on a debian(linux) server and the local file being on a Windows OS causes a compatibility issue and creates the wrong path for the file by appending usr/local/neolane/ (default location of a campaign instance) ahead of the file name.

    To overcome this you can :

    1>. Use a file from a public location like this :

    2>. Else , like you have mentioned , you can have the file on a SFTP server and mention the path of the server here like :

    /sftp/<user>/incoming/<file_name> in place of the public url

    3>. Create a workflow to generate the file on the workflow execution and then export the file to the var/<instance_name>/export folder using the data extraction activity and then use the delivery ,attachment name should be : export/<file_name>

    Hope this helps

    Regards,

    Adhiyan

    23 replies

    Show previous replies
    R
    ramakattAuthor
    Employee
    July 10, 2017

    Hi Adhiyan,

    I was trying to test by using a file from a public location (yet to test the SFTP method, though). Placed the files on my google drive and extracted a shareable link to view the files and pasted the link as shown in the screenshot.

    Got the below error. Not sure, if it accepts, https link from google drive instead of http. Any help?

    R
    ramakattAuthor
    Employee
    July 9, 2017

    Hi Adhiyan,

    Thank you very much for your quick response. I will try this and get back to you with the concerns, if any.

    Thanks,

    Rajesh

    Adhiyan
    AdhiyanAccepted solution
    Employee
    July 9, 2017

    Hello Rajesh,

    This is a known limitation when using calculated attachments uploaded from the local system . The reason is that when the attachment is prepared during delivery analysis , the MTA is responsible for preparing the attachment. The MTA for a hosted environment runs on a debian(linux) server and the local file being on a Windows OS causes a compatibility issue and creates the wrong path for the file by appending usr/local/neolane/ (default location of a campaign instance) ahead of the file name.

    To overcome this you can :

    1>. Use a file from a public location like this :

    2>. Else , like you have mentioned , you can have the file on a SFTP server and mention the path of the server here like :

    /sftp/<user>/incoming/<file_name> in place of the public url

    3>. Create a workflow to generate the file on the workflow execution and then export the file to the var/<instance_name>/export folder using the data extraction activity and then use the delivery ,attachment name should be : export/<file_name>

    Hope this helps

    Regards,

    Adhiyan

    Marcel_Szimonisz
    Marcel_Szimonisz
    New Participant
    November 13, 2023

    Hello @adhiyan .
    if you are using midsourcing server, it seems the attachment is also not found, is there any other way then above mentioned to fix it?

    Marcel

    Terms & ConditionsAccessibility statement

    Loading footer...