<p>Ran into the same issue, asked the support team, and they confirmed it's a bug. </p>

<p>Workaround is to comment out this line:
<a href="https://github.com/barrelstrength/craft-sprout-base/blob/v2/src/app/email/elements/NotificationEmail.php#L481" rel="nofollow noreferrer">https://github.com/barrelstrength/craft-sprout-base/blob/v2/src/app/email/elements/NotificationEmail.php#L481</a></p>

<p>Tried it and it works fine. </p>

<p>They said it would be fixed in an upcoming release.</p>

CC BY-SA 4.0
2018-07-27T16:27:30.630Z
This has been fixed in Sprout Forms v3.0.0-beta.21.
Ben Parizek
CC BY-SA 4.0
2018-07-06T13:04:24.820Z
2018-07-06T13:04:24.820Z
Seb
<p>Dynamic values work in Sprout Forms as of Sprout Forms v3.0.0-beta.21.</p>

<p>You can target any value that is being submitted by your form using the shorthand syntax from your example <code>{email}</code> or object syntax <code>{{ object.email }}</code>.</p>

CC BY-SA 4.0
2019-02-22T18:30:41.543Z
I'm having the same issue in 3.0.0-beta.44, but the linked workaround is no longer accurate.
artmem
CC BY-SA 4.0
2019-02-25T20:47:26.540Z
@sarah3585 we were able to recreate this issue and we'll update this post once a fix is in place
Andre L.
CC BY-SA 4.0
2018-07-27T16:25:52.703Z
2018-07-27T16:25:52.703Z
Ben Parizek
<p>I'm looking to have a Dynamic 'Reply To' for a notification when an entry is saved from a form submissions.</p>

<p>I'm using the below which is what the field is named in my form, but it seems it's not allowed? </p>

<pre><code>{email}
</code></pre>

<p><a href="https://i.sstatic.net/tkgxu.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/tkgxu.png" alt="enter image description here"></a></p>

CC BY-SA 4.0
2019-02-21T13:32:15.767Z
Using sprout forms 3.0.0-beta.44 I get the same validation error.. ( I have a email field with handle email in the form...) [![screenshot](https://i.sstatic.net/7xT1N.png)](https://i.sstatic.net/7xT1N.png)
Pieter-Jan De Bruyne
CC BY-SA 4.0
2019-04-10T14:42:13.127Z
@Pieter-JanDeBruyne This is resolved in the latest release (v3.0.0-beta.50)
Ben Parizek
<plugin-sproutforms>
Using Dynamic values in the Reply To field in Sprout Forms Notifications
# Using Dynamic values in the Reply To field in Sprout Forms Notifications

(Asked by: username_0 on 2018-07-05)

I'm looking to have a Dynamic 'Reply To' for a notification when an entry is saved from a form submissions.
I'm using the below which is what the field is named in my form, but it seems it's not allowed? 
{email}

**Tags:** plugin-sproutforms

> **Comments:**
> **username_1**: Using sprout forms 3.0.0-beta.44 I get the same validation error.. ( I have a email field with handle email in the form...) [![screenshot](https://i.sstatic.net/7xT1N.png)](https://i.sstatic.net/7xT1N.png)  
> **username_2**: @Pieter-JanDeBruyne This is resolved in the latest release (v3.0.0-beta.50)  

---

## 2 answers

### Answer by username_3 on 2018-07-06. Score: 3 | Accepted answer

Ran into the same issue, asked the support team, and they confirmed it's a bug.

Workaround is to comment out this line:
<https://github.com/barrelstrength/craft-sprout-base/blob/v2/src/app/email/elements/NotificationEmail.php#L481>

Tried it and it works fine.

They said it would be fixed in an upcoming release.

> **Comments:**
> **username_2**: This has been fixed in Sprout Forms v3.0.0-beta.21.  

---

### Answer by username_2 on 2018-07-27. Score: 1

Dynamic values work in Sprout Forms as of Sprout Forms v3.0.0-beta.21.

You can target any value that is being submitted by your form using the shorthand syntax from your example `{email}` or object syntax `{{ object.email }}`.

> **Comments:**
> **username_4**: I'm having the same issue in 3.0.0-beta.44, but the linked workaround is no longer accurate.  
> **username_5**: @username_0 we were able to recreate this issue and we'll update this post once a fix is in place  

---

