Timeline for Visualforce Remoting Callback Function
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 20, 2017 at 23:31 | vote | accept | Olivia | ||
| Feb 20, 2017 at 23:31 | comment | added | sfdcfox♦ |
@Olivia it is JS, but you can't do something like this: someFunction( console.log(data); someparam) It's the same basic rules as Apex Code, etc. Each statement has to be written correctly.
|
|
| Feb 20, 2017 at 23:29 | comment | added | Olivia | oh shoot. I thought that you could use console.log anywhere through out the function. I didn't realize that Visualforce.remoting.Manager.invokeAction() was not considered JS. | |
| Feb 20, 2017 at 23:19 | comment | added | sfdcfox♦ | @Olivia your JavaScript is still wrong. You need to pay attention to where you're inserting new code. You put a console.log inside of the parameter list, and along with the semi-colon, you confused the JS compiler again. Try using a JavaScript linter to avoid mistakes like this, or consider using some sort of JavaScript-aware IDE. | |
| Feb 20, 2017 at 23:01 | comment | added | Olivia |
thanks for the documentation and clarification. Is it possible the Visualforce.remoting.Manager.invokeAction is written incorrectly? I am still getting an uncaught reference error when I add this part into the function. When I take it out though the function runs fine.
|
|
| Feb 20, 2017 at 22:15 | history | answered | sfdcfox♦ | CC BY-SA 3.0 |