I want to reference the token from the subject line of the admin email sent when a survey is submitted. Here is what I have been trying:

Basic admin notification subject: {SURVEYNAME} on {SurveyDate} Packet # {TOKEN}

Survey name gets replaced with the actual survey name. SurveyDate is the name of a question on the survey and it also gets replaced with the correct value, in this case it is defaulting to the current date, so at the moment I am getting "06-16-2014".

HOWEVER the token syntax does not appear to work as easily. I have tried:
{TOKEN}
{TOKEN:TOKEN}
{Token}
{token}

At this point I am running out of guesses AND survey responses (I don't want to buy more just for testing) so does anyone have any suggestions?

I really want to have the token in the subject line of the admin email because we use that information to sort the email without having to open it.

Thanks for any help you can give!

Carole

Sounds like a bug.

Please file a bug report and...

1. Give as much information as possible.
2. Provide step-by-step instructions how to reproduce the problem.
3. Provide screenshots and/or a sample survey.
4. Post the link to the bug here so we can follow the progress.

And test with the last version, because we already fix some issue with token in admin email.

PS:
{TOKEN:FIRSTNAME} work for a lot of day (if survey is NOT anonymous).

I can't reproduce for now ... I am using LimeQuery and used up all my responses for the month just trying to get this to work. I have to raise the balance before I can do ANYTHING. Grr! I need a bug refund! Ha, ha!

Hi,

Not sure it's the good link : www.limeservice.com/support

My companies installation seems to work better with respect to embedding token table information into questions, but I am having difficulty on the LimeQuery 2.05 site. I think this behavior is new, I swear it worked last week ...

Attached is a sample survey created in version 2.05+ on the LimeQuery website. I find that references to token table fields fail. In this sample survey I have references in the Group Description text and also in the email template for the basic admin notification.

I think this may be a bug, but the thing is I had this working in this version previously so I am very puzzled.

I first discovered this issue on survey I am working on with a fairly tailored template. However the attached survey utilizes the basic template and I am getting the same behavior.

Something changed on LimeQuery and all of the sudden token table variables are working again, yay!