When I'm trying to use Execute Anonymous with a large chunk of code, the following error pops up:
Line: undefined, Column: undefined
Response to EXEC was : . HTTP CODE[414]
(414 stands for Request-URI Too Long)
Sometimes I just need to remove a few tabs and line breaks to make the request short enough. Is there any way to bypass this limitation, or maybe there is another way to quickly execute a script without creating a new class?
I've run into the same problem myself. I was attempting to run a script that is 525 lines long (feels messy but I'm trying to recreate the actions of a trigger to identify how different values are being calculated in a business process) in the execute anonymous window, and it was giving me the following error message:
Just for kicks, I then tried testing scripts of different length using just "System.debug('Hello world.');" in every line. After a few minutes I found a cutoff point - the script will run with 352 lines of the debug message, but fails at and after 353 lines.
Seems like a bit of a random cut-off point to me, so I suspect that value would change if you had more complex code like loops, SOQL queries, etc. I haven't been able to find any definitive info about the limits of an anonymous window in the Salesforce documentation.
Edit: I also tested this by adding in a few commented lines, and the number of comments affect the cut-off point as well (i.e., 352 debug lines work, 352 debug + 10 comment lines doesn't work).
If you are looking to get this information in a report, you can just create a Report on Tools__c with a filter where you set the operator to 'Contains' and then give the sub-strings you want to search for.
If you are trying to debug each element, I tend to debug them individually as Eric suggested in the comments. I have heard you can use JSON.serialize, which forces the entire object to get thrown into the debug log, but I have not confirmed.
Best Answer
The Developer Console is using the REST version of the Tooling API to perform the execute anonymous call. The length issue is a restriction of how the call encodes the apex into the URL.
It is URL encoding your Apex onto the query string. Clearly there are limits to how long this can be.
I found a few viable alternatives.