Logic replace custom field not saving

Hi @edubois Happy Friday! Do you mind taking a video so I can see what happens when you try to publish and save the changes? Additionally, if you aren’t already, do you mind trying this on the Chrome browser? 

Here is a video : 

@edubois - this comes from another user

Are you using simple logic or advanced logic? it seems to be the simple logic tab and if that is the case, you should probably use the Advanced logic tab and set the variables there. I seem to recall in some obscure documentation or post in here, that this type of variable assignment only works in Advanced Logic

des

I don’t have any calculation logic in there ! 

I’m following this :https://help.typeform.com/hc/en-us/articles/360052365212-How-to-add-and-change-variables-

I see all thoses options, but it’s not saving. I really think it’s just a bug from Typeform. Can they fix it ?

calculation logic = the replacement of a variable with text .. you have an if ..then logic rule which is, in essence, a calculation

What do you mean ? 

Me I’m trying to do exactly this : 

But it’s not saving. Can you try on your side and tell me if it’s saving for you.

just created and it saved properly. 

here is the link to test the form

Perfect ! Great to see it’s working for you. What are the potential reasons why it’s not working in my account ? Because i french ?

je ne sais pas! it could be due to the plan you have, i don’t know.. 

suggest you open ticket with the support desk at this link to get them to take a look inside your account. 

Really weird. I’m on the biggest plan. Clearly a bug. I completed the form you sent me. Thanks

Hi @edubois Were you able to get ahold of the support team to see why the logic wasn’t working? 

Any updates on this? Im facing kind of the same bug here...

@edubois do you mind sharing the solution the support team provided? 

I encounter the same issue (free plan).
I guess it is because of the use of capitals, although the error mentions: “Variable names must start with a letter.” (see attached screenshot, compare @a_1 with the erroneous @A_2)
In this case, the error should state: “No capitals allowed, please use lowercast.” :)
Could the support team please look into this?