<p>Variables in Craft are case sensitive.  You'll run into the same error if you try to output the Craft <code>{{ siteName }}</code> global as <code>{{ SITENAME }}</code>.</p>

<p>Updating the casing to <code>{contactFullName}</code> or <code>{{ object.contactFullName }}</code> should get things working for you.</p>

<hr>

<p>An extra note regarding the comments above. Luke is onto the right answer in the comments, however, one more distinction needs to be made. There are multiple variables available to your Sprout Email templates. To quote the docs linked in Luke's comment: </p>

<blockquote>
  <p>In your notification templates you can use any Twig code that you
  would use elsewhere in your templates. Additionally, Sprout Email
  Notifications give you access to the Notification Email Object (entry)
  and any Dynamic Object provided by the event (object)</p>
</blockquote>

<p>Your variable <code>contactFullName</code> is not a field on your Notification Email Entry, it's a field on your Sprout Forms Submission Entry.  It's correct that you would get an error trying to refer to it as <code>{entry.contactFullName}</code> because 1) the Notification Email doesn't have that field and, 2) the shorthand syntax is going to add the <code>object</code> variable behind the scenes, so the variable would be seen as <code>{{ object.entry.contactFullName }}</code>.</p>

CC BY-SA 3.0
2016-04-28T21:46:21.093Z
2016-04-28T21:46:21.093Z
Ben Parizek
<p>I'm getting the following error:</p>

<p><code>An exception has been thrown during the rendering of a template ("Craft\SproutForms_EntryModel and its behaviors do not have a method or closure named "CONTACTFULLNAME".") in "CONTACT FORM ENQUIRY FROM: {{object.CONTACTFULLNAME|raw}}
</code></p>

<p>The form has the following fields:</p>

<p><code>contactFullName</code>
<code>email</code>
<code>message</code></p>

<p><em>The email notification fields for the first email</em> <code>Contact Form - Thank You</code> message contain:</p>

<p>Subject: <code>Contact Form - Thank You ​{contactFullName}</code></p>

<p>Message: <code>Thank you for contacting us, {contactFullName}. We will be in touch soon.</code></p>

<p><em>And for the other email:</em></p>

<p>Subject: <code>Contact form enquiry from: {contactFullName}</code></p>

<p>Message: <code>You have received an enquiry Enquiry from {contactFullName} - {email} “{message}”</code></p>

<p>Can anyone shed any light onto why this capitalised reference to the CONTACTFULLNAME missing method or closure (by this I presume field) appears in the logs? The form is getting saved, but no email sent due to this message.</p>

CC BY-SA 3.0
2016-04-28T14:37:23.623Z
Running Craft CMS 2.6.2780, Sprout Email 2.2.3, Forms 2.2.5
Adam Menczykowski
CC BY-SA 3.0
2016-04-28T15:21:10.923Z
Have you tried using `{entry.contactFullName}`? Picked this up from the docs here: http://sprout.barrelstrengthdesign.com/craft-plugins/email/docs/notifications/dynamic-values#using-dynamic-values-in-your-notification-templates
Luke Pearce
CC BY-SA 3.0
2016-04-28T15:30:43.417Z
Hi Luke thanks I have just tried swapping out the references to that field with ```{object.contactFullName}```, however that just throws a different error: ```An exception has been thrown during the rendering of a template ("Craft\SproutForms_EntryModel and its behaviors do not have a method or closure named "entry".") in "Contact form enquiry from: {{object.entry.contactFullName|raw}}" at line 1.```
Adam Menczykowski
<plugin-sproutforms><plugin-sproutemail>
Sprout Email not triggering from Sprout Form
# Sprout Email not triggering from Sprout Form

(Asked by: username_0 on 2016-04-28)

I'm getting the following error:

`An exception has been thrown during the rendering of a template ("Craft\SproutForms_EntryModel and its behaviors do not have a method or closure named "CONTACTFULLNAME".") in "CONTACT FORM ENQUIRY FROM: {{object.CONTACTFULLNAME|raw}}`

The form has the following fields:

`contactFullName`
`email`
`message`

*The email notification fields for the first email* `Contact Form - Thank You` message contain:

Subject: `Contact Form - Thank You ​{contactFullName}`

Message: `Thank you for contacting us, {contactFullName}. We will be in touch soon.`

*And for the other email:*

Subject: `Contact form enquiry from: {contactFullName}`

Message: `You have received an enquiry Enquiry from {contactFullName} - {email} “{message}”`

Can anyone shed any light onto why this capitalised reference to the CONTACTFULLNAME missing method or closure (by this I presume field) appears in the logs? The form is getting saved, but no email sent due to this message.

**Tags:** plugin-sproutforms, plugin-sproutemail
> **Comments:**
> **username_0**: Running Craft CMS 2.6.2780, Sprout Email 2.2.3, Forms 2.2.5  
> **username_1**: Have you tried using `{entry.contactFullName}`? Picked this up from the docs here: http://sprout.barrelstrengthdesign.com/craft-plugins/email/docs/notifications/dynamic-values#using-dynamic-values-in-your-notification-templates  
> **username_0**: Hi Luke thanks I have just tried swapping out the references to that field with ```{object.contactFullName}```, however that just throws a different error: ```An exception has been thrown during the rendering of a template ("Craft\SproutForms_EntryModel and its behaviors do not have a method or closure named "entry".") in "Contact form enquiry from: {{object.entry.contactFullName|raw}}" at line 1.```  

---

## 1 answers

### Answer by username_2 on 2016-04-28. Score: 2 | Accepted answer

Variables in Craft are case sensitive. You'll run into the same error if you try to output the Craft `{{ siteName }}` global as `{{ SITENAME }}`.

Updating the casing to `{contactFullName}` or `{{ object.contactFullName }}` should get things working for you.

---

An extra note regarding the comments above. Luke is onto the right answer in the comments, however, one more distinction needs to be made. There are multiple variables available to your Sprout Email templates. To quote the docs linked in Luke's comment:

> In your notification templates you can use any Twig code that you
> would use elsewhere in your templates. Additionally, Sprout Email
> Notifications give you access to the Notification Email Object (entry)
> and any Dynamic Object provided by the event (object)

Your variable `contactFullName` is not a field on your Notification Email Entry, it's a field on your Sprout Forms Submission Entry. It's correct that you would get an error trying to refer to it as `{entry.contactFullName}` because 1) the Notification Email doesn't have that field and, 2) the shorthand syntax is going to add the `object` variable behind the scenes, so the variable would be seen as `{{ object.entry.contactFullName }}`.


---

