Timeline for Call @future from @RemoteAction?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:54 | history | edited | CommunityBot |
replaced http://salesforce.stackexchange.com/ with https://salesforce.stackexchange.com/
|
|
| Nov 23, 2014 at 1:39 | history | edited | Matt and Neil | CC BY-SA 3.0 |
deleted 1 character in body
|
| Nov 23, 2014 at 1:30 | history | edited | Matt and Neil | CC BY-SA 3.0 |
added 149 characters in body
|
| Nov 22, 2014 at 7:11 | vote | accept | Nathan Williams | ||
| Nov 22, 2014 at 7:11 | comment | added | Nathan Williams | Hmm, thanks for digging in. Yes, there must be something funky with the way they created the code to not allow @future. Since I don't have access, I won't know. Thanks for digging in, at least now I know it's possible! I came up with another solution using a trigger, but was much more inelegant than I was going for. | |
| Nov 22, 2014 at 0:55 | history | answered | Matt and Neil | CC BY-SA 3.0 |