Skip to main content
Question

Performance impact custom fields

  • February 19, 2021
  • 2 replies
  • 267 views

GISANCAR
Sidekick (Customer)
Forum|alt.badge.img+8

Are there performance differences on the different implementation types on custom fields?

I’m building a printout that will require quite a few custom fields and I’m pondering the performance differences on the different types. My aim is to build a light impact solution.

If I can retrieve a value using any of Reference, Select and Expression, which is most efficient?

 

This topic has been closed for comments

2 replies

Forum|alt.badge.img+10
  • Hero (Customer)
  • 126 replies
  • February 19, 2021

The efficiency of the action is linked more to the access method used in the database rather than the implementation type of the custom field.  Using functions is convenient, but often the best method (as it pertains to performance) is a query because you have better control over what index you can create an use.

In your case if you are creating many custom fields on one screen, there is not much hope that it will be fast if most of them are lookup fields.


durette
Superhero (Customer)
Forum|alt.badge.img+19
  • Superhero (Customer)
  • 525 replies
  • February 19, 2021

If you’re doing searches against these custom fields, performance is a lost cause. They all get implemented as PL/SQL functions, so even with the best indexing, you’re going to hit PL/SQL to SQL context switches.

 

If you’re worried about selecting a lot of data without doing searches, SQL statements are going to be faster than API calls.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings