Apex Code Development You need to sign in to do that
Don't have an account?
Krzysztof Nowacki Response size exceeded 15MB organization limit suddenly appear
Hi,
Ive got a custom vf pages that were running a OK untill today when the "Response size exceeded 15MB organization limit" error appeared.
What can be the reason? Ive runed sandbox refresing yeastarday and it is In Queue at the moment.Could it be a reason? Any other possibilities What could happened?
Best,
Kris
Ive got a custom vf pages that were running a OK untill today when the "Response size exceeded 15MB organization limit" error appeared.
What can be the reason? Ive runed sandbox refresing yeastarday and it is In Queue at the moment.Could it be a reason? Any other possibilities What could happened?
Best,
Kris
What is on your page? Are you rendering a big list of data? Are you sending back lots of massive images? Does it include Static Resources?
This error message means your page is more than 15Mb big - which is f*cking huge... You would use nearly all of my sisters mobile data allowance for a month in like 20 page refreshes.
What's on the page? If it is data - you need to paginate it, or be a lot more selective in what you send back (selective on the server side)... if you have massive repeating blocks of HTML, Javascript or CSS - consider better use of Classes and inheritence, or pull in Javascript from an external CDN or apex iterators on the client side so you don't send down so much code.
Finally, cut a load out of the page (ie in a sandbox, delete a load of data perhaps?) and the nuse the "F12" developer tools on the "net" tab to see what files are too big for the response.
The page is mostly <analytics:reportChart page showing report charts.
I didnt went into details because it was working OK for 6 months then something happened.
There is some css style inside but when I delated it the error is still there.
:D :D :D
"This error message means your page is more than 15Mb big - which is f*cking huge... You would use nearly all of my sisters mobile data allowance for a month in like 20 page refreshes." :D :D :D
1) https://developer.salesforce.com/forums/?id=906F000000096hcIAA
2) https://twitter.com/forceguru/status/251360097916305408
This error relates to the size of the HTML being produced by your Visualforce page and transmitted to the client browser. It is documented here.
https://developer.salesforce.com/docs/atlas.en-us.pages.meta/pages/pages_controller_lifecycle.htm
Reducing the bindings in your page will not improve this, unless it is reducing the HTML content your page is outputting. Though its always good to keep bindings simple when doing repeated output.
HTML elements vs VF elements. Study the HTML page DOM of the page once loaded (with less data) to see if your outputting any unnecessary HTML tags. Keep in mind the VF components output a lot of HTML tags, so consider what value in a read-only / report use case these are adding. Maybe best to use direct bindings to your state with regular HTML elements, e.g. < span >{!MyData}< /span >, < table > etc instead of the VF components. Although your not hitting a view state issue, this answer also goes into a little more detail on using HTML vs VF components and the benifits, How to reduce a large internal view state / what is in the internal view state?.
http://salesforce.stackexchange.com/questions/4537/how-to-reduce-a-large-internal-view-state-what-is-in-the-internal-view-state
Inline Style Usage. If your using some styling on HTML elements your repeating often, you can put these at the top of the page in a style element or in separate CSS file.
Dynamic Loading. You might also want to consider using JavaScript to perform some client rendering and maybe build your content up dynamically (an advanced option is to load the data as the user scrolls).
Pagination. Depending on your requirements for this page (report vs interactive browse), you may also want to consider using a StandardSetController or custom pagination implementation to let the user page through the data, much like the Salesforce List View UI.
Please let us know if this will help you