I have an org that is hitting the 10 limit of spanning relationships. I know I can up it to 15, but I think that might not be enough.
I know I could rebuild the contracts object with a junction object (I didn't build this in the first place), I'm trying to work out a way to avoid this.
I have created custom report types to get most of the data out just to view , but there are some key formulas that I can't do as I keep getting the error.
I am doing a project (with an external developer, I'm not a coder) to do a sync of the data in Salesforce with an external system sending the data to a REST API endpoint.
If the complex formulas I need are handled within the Apex class that sends the data off to the external system, will that avoid the spanning relationships errors?
The workarounds (https://help.salesforce.com/apex/HTViewSolution?id=000171213&language=en_US) say to use Triggers instead of validation rules, so that leads me to think that code does not have these restrictions?
Am I going to be OK with coding these complex formulas, or do I need to start on a redesign of the whole solution?