That seems weird since the above at a first glance is looking right.
But something in the back of my mind tells me that it should probably be all lowecases so it reads [firstname] instead? I seem to weakly remember having itched my head over this a couple of months back.
We tried setting the alias to lower case as also and nothing. somehow we recognize the alias because if it misspelled he places the wrong name on the subject and if ok its just blank.
None of the fields that we configure in the workflow works, not even to send an email to the customer with the email that was submitted.
Could this be how we are calling the forms?
Html.RenderAction("RenderForm", "UmbracoForms", new { formId = new Guid("16830e09-f017-4ad3-b1c8-02bd6c4a0db1"), theme = "default", includeScripts = true });
We are using Umbraco 7.10.4 and Umbraco Forms 7.0.3
Hmm, ok - Then I'm a bit lost. I think I need to setup an instance with forms 7.x myself in order to figure out if it's a bug or something in the way you're trying to do things. But don't think I can do that untill later this evening.
I'll keep you posted in here if no one else chimes in with some things to try out before then :)
Ok, seems that in the previous answers I have been causing a bit more confusion than what was the intention of course.
BUT! Now I gave it a quick spin and if only my eyes had worked in the first place I would have suggested you to lowercase the alias inside the curly brackets and then I'm 99.9991% certain that it would just have worked for you.
So try doing this {firstname} <-- This should work! So the key is to keep the alias in all lowercase and then it works. The documentation should of course be updated so it's a lot more clear. I'll see if I can manage to do a fix for that one. But I will not do it before you have confirmed that it now works for you :-)
I have attached 4 screendumps showing my process in chronological order.
EDIT: For other who might come across this - Skip the above advice - I've been out of the game for too long and forgot all about the Issue Tracker for forms here: http://issues.umbraco.org/issues/CON
Argh yes! Totally forgot about the tracker...unfortunately it's been a while since I've been active in the forum so this totally slipped my mind somehow. Shame on me :-)
Fingers crossed that HQ will notice your comment - But that of course does not help you here and now.
But isn't there any other way that you can solve your issue? Can you show a screendump of what your desired form setup looks like?
Unable to get field values in email subject.
Hi guys,
I'm creating my first Umbraco Forms form and I can't get the field value to display on the email subject.
If I use the correct field alias the subject is empty.
Hi Vasco and welcome to our :-)
That seems weird since the above at a first glance is looking right.
But something in the back of my mind tells me that it should probably be all lowecases so it reads [firstname] instead? I seem to weakly remember having itched my head over this a couple of months back.
Looking forward to hearing from you.
Cheers, Jan
Hi Jan,
Thank you for your response, but didn't work :(
We tried setting the alias to lower case as also and nothing. somehow we recognize the alias because if it misspelled he places the wrong name on the subject and if ok its just blank.
None of the fields that we configure in the workflow works, not even to send an email to the customer with the email that was submitted.
Could this be how we are calling the forms?
Html.RenderAction("RenderForm", "UmbracoForms", new { formId = new Guid("16830e09-f017-4ad3-b1c8-02bd6c4a0db1"), theme = "default", includeScripts = true });
We are using Umbraco 7.10.4 and Umbraco Forms 7.0.3
Hi Vasco
Hmm, ok - Then I'm a bit lost. I think I need to setup an instance with forms 7.x myself in order to figure out if it's a bug or something in the way you're trying to do things. But don't think I can do that untill later this evening.
I'll keep you posted in here if no one else chimes in with some things to try out before then :)
Have a nice day.
Hello again Vasco
Turns out my memory is all wrong according to the documentation here https://our.umbraco.org/documentation/Add-ons/UmbracoForms/Developer/Magic-Strings/#parsing-umbraco-form-field-items
The example provided there is using curly brackets so you should be able to do {FirstName} in your case.
Hope this helps! :-)
/Jan
Hi Jan,
Once again thank you.
That was our initial approach that didn't work.
Argh sorry! I read saw your initial post as square brackets [] rather than the curly ones! My bad...Will investigate on a clean install now then.
Hi Vasco
Ok, seems that in the previous answers I have been causing a bit more confusion than what was the intention of course.
BUT! Now I gave it a quick spin and if only my eyes had worked in the first place I would have suggested you to lowercase the alias inside the curly brackets and then I'm 99.9991% certain that it would just have worked for you.
So try doing this {firstname} <-- This should work! So the key is to keep the alias in all lowercase and then it works. The documentation should of course be updated so it's a lot more clear. I'll see if I can manage to do a fix for that one. But I will not do it before you have confirmed that it now works for you :-)
I have attached 4 screendumps showing my process in chronological order.
I hope this helps!
Cheers, Jan
Hi Jan,
After banging my head a couple of hours because I was doing everything you said. I discovered a huge bug in this.
So is actually using the Label instead of the Alias.
Here is my field definition:
And here is the workflow that worked:
The outputed HTML also uses the Label to generate a CSS Class.
I guess its working in your case because the label and the alias are the same.
This means I cannot have multiple questions with the same label and using it in the workflow or styling it differently.
do you know how can I report this to Umbraco?
Hi Vasco
Ah, yes that's confusing - I had not thought of that scenario before. Good discovery!
If you're a gold partner then you should have direct support access but can't remember what the case is if you buy single packages.
But I guess that you could always try to reach them at https://umbraco.com/contact-us/ filling out the contact form.
EDIT: For other who might come across this - Skip the above advice - I've been out of the game for too long and forgot all about the Issue Tracker for forms here: http://issues.umbraco.org/issues/CON
h5is
Cheers, Jan
Hi,
Jan thank you, its seems a bug was open in 2016 :|
http://issues.umbraco.org/issue/CON-1208#tab=Comments
This simply doesn't make sense, if we want to update a field name we have to change all the workflow properties were that field is used.
Hi Vasco
Argh yes! Totally forgot about the tracker...unfortunately it's been a while since I've been active in the forum so this totally slipped my mind somehow. Shame on me :-)
Fingers crossed that HQ will notice your comment - But that of course does not help you here and now.
But isn't there any other way that you can solve your issue? Can you show a screendump of what your desired form setup looks like?
/Jan
This is still an issue in Forms version 7.0.6. The updated issue reference (on the newer GitHub tracker) is here: https://github.com/umbraco/Umbraco.Forms.Issues/issues/35
Go upvote it, if this still bugs the heck out of you (as it does me).
The issue is also there in Forms version 8.1.1
is working on a reply...