Extender and Performance

This is a very common question. Extender itself doesn't fundamentally impact the performance of Sage 300. However, when designing scripts, you need to follow some best practices.

  1. Some of the general guidelines applying to Sage 300 views would apply. For example, when using Browse and Fetch for specific records. If you are using the wrong key, the browse can be slow (or in some cases not even return the results you expect). 

  2. When you just need to read records, we find that using CSQRY can improve performance. Refer to the knowledge base article below. Using Browse/Fetch or Read to find records in Sage 300 views.

  3. Regarding separate vs single script, both are possible. Refer to the article below highlighting some elements to take into consideration to decide on the best approach. Extender tips - multiple scripts vs one script 

  4. New features in Extender PU11 to reduce potential performance impact of scripts– we will review separately .  Performance tips (new options in PU11)

  5. If you are adding fields to the grid, we suggest you list the fields that trigger the setOnGetText function. This will reduce potential delay in refreshing fields.

Copy 
grid.setOnGetText(self.onGridGetText, "Course|Buyer|Course Type|Location|Division|Trainer|Region")