Error approving my emails | Community
Skip to main content
V
VKailash
New Participant
March 23, 2021
Solved

Error approving my emails

  • March 23, 2021
  • 1 reply
  • 2146 views

 

Hi 

 

I recently imported the program from sandbox to marketo production & removed all dynamic content & segmentation for the email assets, after the program was imported in our production instance I added dynamic content & segmentation to the email assets. This issue if that none of the emails are getting approved and is throwing in errors mentioned in the screenshot.

Errors message 

  •  attribute map field with key 3315 not found
  • attribute map field with key 2627 not found

 

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 Oz_Platero

 Hello @vkailash ,

 

Those Key values will likely only make sense to Marketo support.

 

For you start troubleshooting by:

Going to the template and read through he code and remove any fields or adjust the names of fields to match your new destination.  Mostly like you have similar field references, but either the field doesn't exist where you imported to or the spelling might be slightly different.

Then read through the code on the email as well.

 

In a nutshell double check that any field references made; such as tokens actually have a 100% match to what exists in your new destination. 

example:

{{lead.custom field1}}

vs

{{lead.customfield1}}

 

Thank you,

Oz

1 reply

Oz_Platero
Oz_PlateroAccepted solution
New Participant
March 23, 2021

 Hello @vkailash ,

 

Those Key values will likely only make sense to Marketo support.

 

For you start troubleshooting by:

Going to the template and read through he code and remove any fields or adjust the names of fields to match your new destination.  Mostly like you have similar field references, but either the field doesn't exist where you imported to or the spelling might be slightly different.

Then read through the code on the email as well.

 

In a nutshell double check that any field references made; such as tokens actually have a 100% match to what exists in your new destination. 

example:

{{lead.custom field1}}

vs

{{lead.customfield1}}

 

Thank you,

Oz

    Terms & ConditionsAccessibility statement

    Loading footer...