Custom settings

Custom settings and global variables are similar but custom settings can also be used in Application Engine processes, OLAP mappings, and in relational modeling. Custom settings can be encrypted if they are used to hold sensitive information such as passwords.

A primary use of custom settings is in designing reports that are used to configure applications. Such configurations can include, for example, specifying a standard reporting period. Or, it might be necessary to rename certain cubes, dimensions or data connections. Custom settings, like global variables, enable you to make such changes for all users.

Custom settings can be used to parameterize load queries, scripts, and cube mappings. Custom settings can reference a single value or multiple values.

Note: You cannot add custom settings to restricted applications such as Infor EPM Business Applications.

Use this syntax to incorporate a single-value custom setting into a script:

@CustomSettings.<setting_name>

For example:

delete * from Table where ModifiedDate >@CustomSettings.LoadFromDate