FinancialForce.com can be detrimental to the performance of your Salesforce.com Org
FinancialForce.com first appeared in 2009 and is a partner with Salesforce.com. It’s also worth noting that Salesforce.com does not have any financial interest in FinancialForce to date.
FinancialForce.com is a system built on top of the Salesforce.com platform. There are huge benefits to FinancialForce.com in doing this, mainly access to the same database and sales data without needing any integration into Salesforce.com and Reporting and Dashboards being already built by Salesforce.com
The one thing, not often spoken about is the lacklustre performance FinancialForce.com has and yes it can take its toll on your entire Org. We explain below.
Every Org on a Salesforce.com instance is allocated adequate CPU and RAM resources to run Salesforce.com adequately. This includes custom Workflows, Apex Triggers, Apex Classes, API Calls and Custom Objects within the governed limits.
It’s also a given that accounting software products are very CPU intensive. For example, when posting a journal or running batches they either trigger and calculate immediately or they form a background process that is queued and executed when there are adequate resources available to do so.
This is where these 2 worlds collide. When you install FinancialForce.com into your Saleforce.com Org the CPU and RAM allocation is not increased, therefore what you now have is an accounting system that is CPU intensive and leeches resources that would otherwise be allocated to the proper running of your Salesforce.com Org.
FinancialForce.com introduces 209 Objects, 79 Tabs, 351 Visualforce pages, 160 Apex Triggers and 3126 Apex Classes.
The end result is that you now have your Salesforce.com Org and FinancialForce running very slow. In fact so slow that if you are doing any Apex development by yourself you might actually see some timeouts while trying to edit and save your code.
How slow is slow? Try approximately 3 minutes to search for a Business Name where there are only 18 records in the database. FinancialForce.com is not always this slow and some improvement can be seen around 2 AM in the morning. It seems to all depend on what other processes are running in the background at the time.
Mind you this could all be avoided if more CPU and RAM resources were allocated to the Org, and of course, if FinancialForce.com did not leech the resources from the Salesforce.com Org.
Whos problem is it? It’s a fundamental design flaw in FinancialForce.com. We believe there are no agreements in place between Salesforce.com and FinancialForce.com should an Org require more CPU and RAM resources to be able to adequately run both the Salesforce.com platform and FinancialForce.com.
It’s worth asking about this if you a considering buying, and get something written in the contract that FinancialForce.com will take responsibility for fixing such speed issues should they occur.
The FinancialForce.com Support Desk has been horrendous, with no phone number to call. It’s a case of submitting a ticket and someone will get to it. This often causes a lot of going back and forwards and to be honest, a waste of time. We’ve not had any helpful and delightful support agents thus far.
There are other Financial ERP products around that will integrate into the Salesforce.com platform quite nicely. We’d recommend shopping around and get your IT people onboard a meeting before buying. It’s truly important that you do not invest in a product that leeches resources from the proper running of Salesforce.com