This technical note outlines the Automatic Mapping feature in Strategy Architect 9.4.x and how it behaves in different scenarios.

When you create the expression, you can select Automatic or Manual mapping method. Automatic mapping selects for you all available tables that contain the columns being used in the expression as source tables. Manual mapping means that you manually select each table that contains the column used in the expression. Strategy recommends you choose Automatic if you are unsure what tables contain the column used in the expression.
The default mapping method for the first expression in a form is Automatic. The default for each subsequent expression created is Manual. If you define a constant as an expression when creating an Implicit attribute, you must set the mapping to Manual.
If you select the Automatic mapping method when you are adding new tables to the project through Warehouse Catalog, this attribute is mapped to those new tables if they contain the columns used to define the expression. This mapping method saves you from manually mapping objects to these new tables.

You can select the options that guide the Warehouse Catalog to map schema objects to new tables, using the following options:
In order for schema objects to map automatically to new tables added to the project, or when a column that didn't exist previously is added to an existing table after the table's structure is updated, the following conditions must be satisfied:
If any of the above are not satisfied, then automatic mapping will not occur. In addition, if a schema object references a table which is not selected as a source table, automatic mapping will not check it as such, as there may be certain source tables that are not meant to be mapped to certain attributes and facts. In order to force the GUI to select all source tables for a particular form expression, one must do the following: