I'm working on a scheduled script in which I load ...
# suitescriptb
b
03/27/2020, 2:13 AMI'm working on a scheduled script in which I load a file and use the File.lines.iterator(), when I go over each line with iterator.each(function(line) I lose all my variables. Should I be using the iterator or should I get data from each file of the line a different way?
b
battk
03/27/2020, 2:14 AMyou can share your code for more specific help
battk
03/27/2020, 2:14 AMbut i would say your variables should be declared outside of your iterator function
b
b
03/27/2020, 2:16 AMthey are
b
battk
03/27/2020, 2:17 AMwhich variables are having problems
b
b
03/27/2020, 2:18 AManything declared outside of i.each(function (line){}); is not available
b
battk
03/27/2020, 2:20 AMpick one, your variables are badly named
battk
03/27/2020, 2:20 AMim having trouble picking which ones are important
b
b
03/27/2020, 2:21 AMthey are all important
b
battk
03/27/2020, 2:22 AMpick one which doesnt have a value
battk
03/27/2020, 2:22 AMtraditionally 1 character variable names are used as temporary values
battk
03/27/2020, 2:22 AMlike loop indexes
b
b
03/27/2020, 2:23 AMnone of them do outside of the iterator, I'm in the debugger and once I am inside the lines.iterator all my other local variables are gone, poof, bye
b
03/27/2020, 2:23 AMok, I will fix my variables later but need to get the script to work first
b
03/27/2020, 2:24 AMI should say none of them exist inside the file.lines.iterator, unless I've declared them there
b
battk
03/27/2020, 2:27 AMthe suitescript debugger tends to make variables from the call stack hard to find
battk
03/27/2020, 2:27 AMare you saying that you can't debug the variables, or that your variables are undefined when you expect them to have a value
battk
03/27/2020, 2:30 AMif you are talking about the debugger, change the value of the call stack field to see variables higher up the call stack
b
b
03/27/2020, 2:31 AMI see now, ok, thank you, that's frustrating
16 Views