# Get All Get Functions

**URL:** <https://the.fmsoup.org/t/get-all-get-functions/3508>\
**Category:** Sample files & code\
**Tags:** custom-function, get-functions\
**Created:** [April 17, 2023, 3:36am UTC](https://the.fmsoup.org/t/get-all-get-functions/3508 "2023-04-17T03:36:57Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![tonywhitelive](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/tonywhitelive/32/208_2.png) [@tonywhitelive](https://the.fmsoup.org/u/tonywhitelive)\
**Post date:** [April 7, 2024, 6:04pm UTC](https://the.fmsoup.org/t/get-all-get-functions/3508/6 "2024-04-07T18:04:39Z")

</div>

Good topic, post, and replies..

Timely, as we are using a pre-pre-FM 16 version that is on the To Do list for a modernization.

We use this type of Calculation/Custom Function as part of our HelpRequest system. Currently we "Get" info from 3 scopes: Script, File&Layout, and Environment/Install passing them along the ScriptStack and writing them out to fields in a HelpRequest record.

We also add some items:

- Script Comment
- @scriptID
- @layoutID
- DatabaseNames
- WindowNames
- etc.

Might (or might not) be good to break this code up by "scope".

- Would that make the code much more efficient?
- Easier to upgrade as new Get ( Functions ) ship, for example, Get ( ScriptStack ) and Get ( DockDetails ) ;-0 ?

This Scope InfoG probably has a few errors (and is obviously not up to date)

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/fmsoup/original/2X/f/fb3e0e0df8e047c2c69b958cceeece1a62c2e0bd.png)

---

_[View the full topic](https://the.fmsoup.org/t/get-all-get-functions/3508)._