SOLVED
If/Else Multiple Conditions - or Switch??
1 Accepted Solution
Correct answer by
Hi,
Here is the form back to you: http://www.assuredynamics.com/wp-content/uploads/2011/07/2011-07-11-ShareVersion_Form.pdf
I will delete the link once you have the form.
There were a few issues:
The rType radio buttons were all named the same as the exclusion group, so this is why it was resolving the node. I have renamed them:
On the issue of radio buttons, there were three Yes/No questions where the choices were not in an exclusion group. I have paired these:
Objects, like nSavings were in unnamed containers, which makes scripting difficult (need to resolve the node):
In the script you are declaring a variable, which has the value of the object that contains the script. Then you are referring to that variable in order to set the value of the object. This is akin to the getField() method in Core/AcroForm JavaScript, but will NOT work here. Instead I have referred to the object using "this.rawValue".
The final script is here:
var myVal = sfrmMainSub1.sfrmMain2.tbMainInfo.section1.rowEstimates.tblEstimates.Row1.sfrmEstimates.nSavings.rawValue;
var myType = xfa.resolveNode("sfrmMainSub1.sfrmMain2.tbMainInfo.Row4[8].sfrmIdeaCAT.rType").rawValue;
// first check if Type B
if (myType === "2")
{
this.rawValue = "1";
}
// then work through savings levels
else if (myVal >= 1000 && myVal <= 9999)
{
this.rawValue ="1";
}
else if (myVal >= 10000 && myVal <= 24999)
{
this.rawValue ="2";
}
else if (myVal >= 25000 && myVal <= 99999)
{
this.rawValue ="3";
}
else if (myVal >= 100000 && myVal <= 999999)
{
this.rawValue ="4";
}
else if (myVal >= 1000000)
{
this.rawValue ="5";
}
else
{
this.rawValue ="0";
}
I have made the saving classification checkboxes a light grey, so as to indicate that the user does not click these choices. I have also set the Type to Calculated - Read Only in the Object > Value palette.
Lastly, I have changed around the script for the Project Number-Year. Basically the way it was set up if a form that was filled in this year (2011), was opened next year, the reference would automatically change to Project Number-2012. I have changed it to always used the year from the submitted date.
I hope that this is now working for you,
Niall
Can you tell I'm a noobie . . . 
don't know why I'm resolving the rType object except that's what it gave me when I held the contol key and clicked on it to get the address, so I don't know what I'm doing. When I add .rawValue to it,
var myType = xfa.resolveNode("rType").rawValue; the code for the calculations stops working again, I do not understand why declaring the variable (in this case haven't used it yet, can't get past the declaration) breaks the code that was working. I tried to follow the instructions for this,
console.println("myType is: " + myType);but am missing understanding how to implement, as nothing seems to happen. Have been studying declaring variables, but no luck yet, and have surely gotten myself into a mess on this one, so sorry I am not there yet.
Hi,
Can you share your form?
If so, upload it to a file sharing site like Acrobat.com and then publish it. You can then post the published URL here:
Niall
Correct answer by
Hi,
Here is the form back to you: http://www.assuredynamics.com/wp-content/uploads/2011/07/2011-07-11-ShareVersion_Form.pdf
I will delete the link once you have the form.
There were a few issues:
The rType radio buttons were all named the same as the exclusion group, so this is why it was resolving the node. I have renamed them:
On the issue of radio buttons, there were three Yes/No questions where the choices were not in an exclusion group. I have paired these:
Objects, like nSavings were in unnamed containers, which makes scripting difficult (need to resolve the node):
In the script you are declaring a variable, which has the value of the object that contains the script. Then you are referring to that variable in order to set the value of the object. This is akin to the getField() method in Core/AcroForm JavaScript, but will NOT work here. Instead I have referred to the object using "this.rawValue".
The final script is here:
var myVal = sfrmMainSub1.sfrmMain2.tbMainInfo.section1.rowEstimates.tblEstimates.Row1.sfrmEstimates.nSavings.rawValue;
var myType = xfa.resolveNode("sfrmMainSub1.sfrmMain2.tbMainInfo.Row4[8].sfrmIdeaCAT.rType").rawValue;
// first check if Type B
if (myType === "2")
{
this.rawValue = "1";
}
// then work through savings levels
else if (myVal >= 1000 && myVal <= 9999)
{
this.rawValue ="1";
}
else if (myVal >= 10000 && myVal <= 24999)
{
this.rawValue ="2";
}
else if (myVal >= 25000 && myVal <= 99999)
{
this.rawValue ="3";
}
else if (myVal >= 100000 && myVal <= 999999)
{
this.rawValue ="4";
}
else if (myVal >= 1000000)
{
this.rawValue ="5";
}
else
{
this.rawValue ="0";
}
I have made the saving classification checkboxes a light grey, so as to indicate that the user does not click these choices. I have also set the Type to Calculated - Read Only in the Object > Value palette.
Lastly, I have changed around the script for the Project Number-Year. Basically the way it was set up if a form that was filled in this year (2011), was opened next year, the reference would automatically change to Project Number-2012. I have changed it to always used the year from the submitted date.
I hope that this is now working for you,
Niall
Got the form, thank you so much, yes, that is exactly how I was needing it to behave. I sure have a lot to learn, the form is very helpful to understand what I was doing wrong with my radio buttons and naming containers. Also, in looking at your code and logic, I was making things way too complicated - first you checked to see if Type B was '2' before running the other value checks.
Thank you for catching the problem with the year, too, I hadn't thought about that, but am sure it would have cropped up next year, and appreciate your help very much.
Thank you, Cathy
