PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Dropdown values changed when sent in notification

  1. kevinmcgillivray
    Member

    Hi, guys. I love GravityForms but I'm running into a problem with notifications:

    I'd like to send the user a link to a file based on what they select from a dropdown field. I set the dropdown up so the VALUES in the dropdown are the URLs of the files. For example, "www.somedomain.com/download/my+download". The user notification will then send them the value of the dropdown so they can then download the file.

    The problem is that the email arrives with "my download" instead of "www.somedomain.com/download/my+download" so Gravity Forms appears to be stripping out part of the value at some point. I've checked and the entire link value is stored in the form "entries" after submission.

    How can I get the form to email the entire value/link to the user? Is there a better way to accomplish what I'm trying to do?

    Thanks!
    Kevin

    Posted 10 years ago on Tuesday April 5, 2011 | Permalink
  2. Are you using the {all_fields} variable or are you selecting each field individually and making a custom notification email?

    The {all_fields} variable shows the user friendly names by default, not the values.

    But if you want to output the value of that field you can output it's value individually using the "Insert Form Field" variable and then changing it to output the value.

    For example normally it may look like this:

    {My Dropdown:1}

    You would change it to this:

    {My Dropdown:1:value}

    That would output the value rather than the user friendly label/name.

    Posted 10 years ago on Tuesday April 5, 2011 | Permalink
  3. kevinmcgillivray
    Member

    Thanks, Carl. That did the trick!

    Posted 10 years ago on Tuesday April 5, 2011 | Permalink

This topic has been resolved and has been closed to new replies.