I’m building a giant financial analyzer where each entity requires ~200 calculated results. My question is: Should I create Formula fields for each calculation (most intuitive/straightforward approach), OR should I create Rules to update ~200 editable fields as needed (seemingly more efficient, but maybe not)?
I guess I don’t understand exactly how/when formulas get triggered for recalculation. Presumably initial load times would be much faster with ‘static’ fields, but I don’t like the UX of showing editable fields that are actually/functionally calculated instead. I should note that we’re not talking about ‘simple’ math operations either, but rather heavy use of the Power function to recreate [missing] CUMIPMT and CUMPRINC equivalents for various mortgage/loan scenarios.
68 as of today, but I’ll be adding 1 or 2 daily as I continue analyzing more & more multifamily apartment deals for potential acquisition & management. Thanks for asking!
*Oh also, each entity has another ~100 truly editable fields, so about ~300 fields in total. AND each parent entity has several children (related subtables for itemizing income, expenses, rehab, etc., actual-v-proforma), but they’re much simpler & negligible computationally.
You should be safe with formulas then. For 10K+ entities and 200 formulas maybe it would be not so good, but for this amount it should be pretty safe. However, I am not sure we have accounts with 200 formulas per database, so you will be a pioneer here.
