How Extender works with Sage 300 

Extender interacts with the Sage views and the Sage desktop UI.

Activating Extender

Activating Extender in Sage Admin Services creates a VI record in CSAPP Table.

Extender also changes the roto.dat file in the Sage 300 > VIxxA folder and in the Shared Data folder.

When you add scripts to the desktop, Extender amends the grp.dat folder.

This is why you are prompted to restart the Sage desktop when adding new configuration in Extender.

Running scripts

Scripts are saved in the database.

At runtime, they are cached in the user’s temp folder %LOCALAPPDATA% on a local machine for performance reasons. You do not need to copy files manually on the server or the workstation.

Option to configure wherE scripts are checked out

With the latest PU, you can configure where to cache the files by updating a registry entry on the Sage 300 server. This only needs to be done if you have security issues on the %LOCALAPPDATA% folder. This is useful on sites with third party modules that run in IIS, such as AutoSimply.

https://orchidsystems.zendesk.com/hc/en-us/articles/360001591616-Extender-checkout-path-configure-where-checked-out-scripts-are-saved-

Checkout tips

  • When you check out a script, that special version of the script is run while checked out. The checked out script is run from the user’s temp folder.

  • Recommend you don’t leave scripts checked out when doing data maintenance.

  • Best Practice to check in or undo checkout regularly.

Tip: Recommend you work on a separate test server, not just a test database.