Try n*3 instead of n3
To quote from the docs
"
(I love the use of the expression crazy talk)
Hi.
Thanks for your answer!
The "n3" is a variable therefore it is written this way.
I'm getting the correct calculation in case I use formula y ={=10*{n1}} (the n1 is variable as well)
In my example to make the function work I have to open parentheses: x ={={n3}*100+3*100} which is not logical and not useful.
I trued all possible ways to enter the formula containing parentheses and each time I got the syntax error.
It seems like the round parentheses are those that cause the problem. I thought maybe there should be some special latex character to create the complex formulas?
For example ## was used in 1.9 version and there was an ability to enter my formula without opening the parentheses;
Could you please help me with it?
Thanks.
I just tested this case, and it works fine:
Question text: An equation: x = {=({n3}+3)*100}. That should be OK.
Answer: {n3}
(This is a stupid question, I realise, but I was just testing.) I am using Moodle 2.8.1 here.
I suspect the change that made this work was https://moodle.org/mod/forum/discuss.php?d=264266. You need to upgrade.
Thanks for your answer.
I use 2.7.1 (Build: 20140714) - the version that is marked as fixed; and it is still reproducible there.
So you suggest to update my moodle version?
Jack, a year has past since you final post fell on deaf ears - I'm hoping you may have managed to find a solution? As you might expect, I'm stuck at present trying to get around the same error message for a formula that worked fine until I substituted an explicit value (15) with a variable {A1}. Can you spot anything obvious I might be doing wrong?
Illegal formula syntax starting with '((((((-(0.45))/6)*(pow((9.539),3)))+({A1}*(pow((9.539),2))))+((0)*(9.539)))+(0))'
If you remove redundant brackets from that, I think you get to
-0.45/6*pow(9.539,3)+{A1}*pow(9.539,2)+0*9.539+0
which is more readable, and seems fine.
I don't know why that is failing to validate. I just checked the code, and it seems fine.
Can you try some alternate variable names, like a1 or aa, to see if they work any better? (A1 should be an allowed variable name, but I think it is worth trying some others to see if it makes a difference.)
However I got
Hi Tim,
Thanks for the advise about removing redundant brackets. They had been 'brought across' with a Respondus import.
We found we were able to prevent the error message being displayed by reverting back to the constant value originally used in the formula. In other words, we decided against substituting a value for a variable as it seemed highly likely that introducing a variable after the question had been created could be problematic.... particularly as we had un-intentionally created a shared dataset for the variable, making it a global variable not declared at the outset. Does that seem like a reasonable assumption to you?
