Global describe methods

[nicolas1bruno]

As salesforce recommends
"Avoid using Schema.getGlobalDescribe() in Apex. This method causes unnecessary overhead, decreases performance, and increases the latency of the associated entry point."

Some classes needs to be refactored

[ImJohnMDaniel]

@nicolas1bruno -- thanks for reaching out. Let me circle up with the others and get back to you.

[ImJohnMDaniel]

G'day @nicolas1bruno -- A couple of questions.

1. Can cite your references to Salesforce documention where you say that Salesforce recommends this. We want to ensure that we are all referencing the same source.
2. Do you have any benchmarks about how much performance degradation you are seeing? Especially considering scenarios where the FFLIB framework is caching global describe results in the process thread.
3. Do you have any recommendations as to which classes would need to be refactored based on the performance impacts that you are seeing?

Thanks for the help.

[brandbarr]

@ImJohnMDaniel - not OP but this may be what they are referencing. It's in the ApexGuru rules.

https://help.salesforce.com/s/articleView?id=xcloud.apexguru_antipattern_schema_getglobaldescribe_not_efficient.htm&type=5

[ImJohnMDaniel]

Thanks @brandbarr. I am familiar with what you referenced there and other items. At the moment, I am reluctant to make any changes until we can get some repeatable benchmarks about the reported performance degradation. That will help us determine if it really is worth it to swap out the Schema.getGlobalDescribe().