<?xml version="1.0" encoding="UTF-8"?><rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
> <channel><title>Comments on: Breaking Formula Compile Size Limit</title> <atom:link href="http://salesforce.phollaio.com/2007/02/16/breaking_formula_compile_size_limit/feed/" rel="self" type="application/rss+xml" /><link>http://salesforce.phollaio.com/2007/02/16/breaking_formula_compile_size_limit/</link> <description>The hows and whys of Salesforce.com</description> <lastBuildDate>Fri, 23 Oct 2009 22:08:51 -0700</lastBuildDate> <generator>http://wordpress.org/?v=2.8.5</generator> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>By: Eric</title><link>http://salesforce.phollaio.com/2007/02/16/breaking_formula_compile_size_limit/comment-page-1/#comment-19</link> <dc:creator>Eric</dc:creator> <pubDate>Tue, 20 Feb 2007 20:32:51 +0000</pubDate> <guid
isPermaLink="false">http://salesforce.phollaio.com/2007/02/16/breaking_formula_compile_size_limit/#comment-19</guid> <description>Some words of caution:
1) The compiled size limit is there for a reason.  The database has hard limits on the maximum size of SQL statements (64K).  If one of your users creates a report joining a couple objects, each of which has several huge formula fields, your users may hit this limit at run-time.
2) The technique described here is exploiting a bug in the max compile size validation.  This bug may be fixed at any time, causing the formulas to no longer run.A preferable workaround for the compiled size limit (for Enterprise &amp; Unlimited Edition customers) is to use Workflow Field Update actions to store formula results in database fields (number, currency, text, etc.) that can then be referenced in other formulas.Cheers,
Eric Bezar
Apex Platform Product Management</description> <content:encoded><![CDATA[<p>Some words of caution:<br
/> 1) The compiled size limit is there for a reason.  The database has hard limits on the maximum size of SQL statements (64K).  If one of your users creates a report joining a couple objects, each of which has several huge formula fields, your users may hit this limit at run-time.<br
/> 2) The technique described here is exploiting a bug in the max compile size validation.  This bug may be fixed at any time, causing the formulas to no longer run.</p><p>A preferable workaround for the compiled size limit (for Enterprise &amp; Unlimited Edition customers) is to use Workflow Field Update actions to store formula results in database fields (number, currency, text, etc.) that can then be referenced in other formulas.</p><p>Cheers,<br
/> Eric Bezar<br
/> Apex Platform Product Management</p> ]]></content:encoded> </item> <item><title>By: Scott</title><link>http://salesforce.phollaio.com/2007/02/16/breaking_formula_compile_size_limit/comment-page-1/#comment-17</link> <dc:creator>Scott</dc:creator> <pubDate>Fri, 16 Feb 2007 17:11:45 +0000</pubDate> <guid
isPermaLink="false">http://salesforce.phollaio.com/2007/02/16/breaking_formula_compile_size_limit/#comment-17</guid> <description>FYI - I am quite sure the formula field compile size is being increased to 5K with the Spring &#039;07 release.</description> <content:encoded><![CDATA[<p>FYI &#8211; I am quite sure the formula field compile size is being increased to 5K with the Spring &#8216;07 release.</p> ]]></content:encoded> </item> <item><title>By: Perspectives on Salesforce.com &#187; Workaround to the formula compile size limit</title><link>http://salesforce.phollaio.com/2007/02/16/breaking_formula_compile_size_limit/comment-page-1/#comment-16</link> <dc:creator>Perspectives on Salesforce.com &#187; Workaround to the formula compile size limit</dc:creator> <pubDate>Fri, 16 Feb 2007 17:10:13 +0000</pubDate> <guid
isPermaLink="false">http://salesforce.phollaio.com/2007/02/16/breaking_formula_compile_size_limit/#comment-16</guid> <description>[...] The Decoding Salesforce blog  has a good post on working around the formula compile size limit. In short, it&#8217;s a way to span your large formula across 2 formulas and compile them in a particular sequence so Salesforce doesn&#8217;t realize its over its limit. Nice hacking! [...]</description> <content:encoded><![CDATA[<p>[...] The Decoding Salesforce blog  has a good post on working around the formula compile size limit. In short, it&#8217;s a way to span your large formula across 2 formulas and compile them in a particular sequence so Salesforce doesn&#8217;t realize its over its limit. Nice hacking! [...]</p> ]]></content:encoded> </item> </channel> </rss><!--
This site's performance optimized by W3 Total Cache:

W3 Total Cache improves the user experience of your blog by caching
frequent operations, reducing the weight of various files and providing
transparent content delivery network integration.

Learn more about our WordPress Plugins: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk
Database Caching 0/10 queries in 0.072 seconds using memcached

Served from: apache2-fungi.pellegrino.dreamhost.com @ 2010-03-10 23:10:33 -->