Send emails using Salesforce Reports based on Custom Object

Question

I want to send emails using a Salesforce Report which is based on Custom Report. I have created an AMP Script Code in order to fill some fields but I don't receive the email. This is the code:

%%[ VAR @rs, @row, @value, @date, @DateP1 
SET @date = AttributeValue("TargetX_SRMb__Application__c:Id") 
SET @rs = RetrieveSalesforceObjects('TargetX_SRMb__Application__c', 'Payment_Deadline_1__c', 'Id', '=', @date) 
IF RowCount(@rs) == 1 THEN 
SET @row = Row(@rs, 1) 
SET @value = Field(@row, 'Payment_Deadline_1__c') 
SET @DateP1 = FormatDate(@value,"l","","en-gb") 
ELSE 
SET @value = 'error' 
ENDIF ]%%

And the report is:

If I test the email using a Data Extension with the name of Salesforce fields, the email is well mapped but when I send the email to the report population, the email doesn't arrive.

Is anyone having the same issue? There is a way to solve it? I can't create a profile attribute with Application Id because it isn't in the Contact Object.

Can somebody help me?

Thank you, Anna

Answer 1

Two things here:

1. You're using AttributeValue("TargetX_SRMb__Application__c:Id") - this fields has to be present either as a Profile Attribute or in the Sendable Data Extension. If this field is not present in your report (which creates a temporary Data Extension), the script won't be able to find this value and the send will fail. Try using a lookup to a Synchronized Data Extension if this field is not present in your Sendable DE. If this is a separate object or a field on an object which isn’t yet synchronized, synchronize it as well in Contact Builder. If this field is present in your report, find the underlying Data Extension and check the exact field name in that DE, not in the report, and use that field name in the AttributeValue function.

2. You shouldn't use RetrieveSalesforceObjects in an email. It might work fine when you send out a test, but then if you send this email to a larger audience, it will take ages for those emails to send. Use a lookup to a Synchronized Data Extension instead.