Timeline for Governor limit SOQL 101 being suppressed. How?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 21, 2014 at 4:51 | comment | added | Matt Lacey♦ | But the code for leadconvert is not necessarily running in the same context as the user's session. | |
| Aug 21, 2014 at 4:09 | comment | added | byadav | Hi, I agree that asyncronous method comes into picture when governor exception is being shown only in Debug logs and not on UI. However I confirm that there is no future method call involved and I can see only one log generated for 'leadconvert.jsp'. If it would have been on different context or in future method then two or more different debug logs would have been generated. | |
| Aug 15, 2014 at 9:19 | comment | added | brovasi | Just want to add one thing is you can increase the number of SOQL now for future method with the following code : @future(limits='2xSOQL') OR @future(limits='3xSOQL') | |
| Aug 15, 2014 at 9:01 | comment | added | Alex Tennant |
This is correct as the standard Lead Convert process uses a number of @future calls to do it's work.
|
|
| Aug 15, 2014 at 0:50 | history | answered | Matt Lacey♦ | CC BY-SA 3.0 |