This article describes the following topics:

There are three ways to access the advanced settings.

Update the specific nodes settings, then click "Update" to save the changes.

There are different options for setting the node field type. This determines the method of inputting values in the table. The default type is "Input Field". To change the Field Type, select the option from the drop-down menu:

When a node field type is set to "Input Field", any value can be entered into a given time step. This is the default setting for new variables and constant nodes.

When a node field type is set to "Single-Select", values can be entered by selecting from a drop-down in the table. Only one selection is allowed for a given time step. The list of options for the drop-down is set by selecting a specific column within a Source View that serves as the reference. Tip: Use the list component template from the Logica Template Library to quickly build a List View.

There are different options for setting the node format. This determines how values are displayed in the table. This format applies to all views where a given node is displayed.

To change the format, select the option from the drop-down menu:

When a node format is set to "Number", no symbols are displayed. The optional Decimals field determines the rounding (display only).

When a node format is set to "USD", a USD dollar sign is displayed. The optional Decimals field determines the rounding (display only).

When a node format is set to "Percentage", a percent symbol (%) is displayed. The optional Decimals field determines the rounding (display only).

When a node format is set to "Boolean", the values display as 1 (TRUE) and 0 (FALSE).

When a node format is set to "Text", the values display as text strings.

When a node format is set to "Date", the values display as dates (YYYY-MM-DD).

When a node format is set to "Period", the values display as the model periods.

There are several options for time-based aggregation and disaggregation of node values.

The options available are determine by the type of model:

Time-based aggregation involves rolling up a lower-level value to a higher-level value.

The value displayed in the aggregation column is the sum of the node values for a given period.

Example: in a monthly model, the Quarterly column will add up January to March.

The value displayed in the aggregation column is the first value in a given period.

Example: in a monthly model, the Quarterly column will use the value from January.

The value displayed in the aggregation column is the last value in a given period.

Example: in a monthly model, the Quarterly column will use the value from March.

The value displayed in the aggregation column is the average of the values in a given period.

Example: in a monthly model, the Quarterly column will use the average value from January to March.

The value displayed in the aggregation column is calculated based on the formula.

Example: in a monthly model, the Quarterly column will divide the SUM of Numerator from January to March by the SUM of Denominator from January to March. The example below also shows the difference between Calculated and Average.

Time-based disaggregation involves breaking down a higher-level value to a lower level value. This is used when a node is set to have an input at the higher aggregation level, and the lower-level period values are calculated.

The input value in the aggregation column is divided evenly across the lower-level periods.

The input value in the aggregation column is the same value as the lower-level periods.

There are different options for setting the node variance convention. This determines how variance values are calculated and displayed in the table. This format applies to all views where a given node is displayed. See this article for how variance is calculated.

To change the variance convention, select the option from the drop-down menu:

The default variance is calculated using the default formula found here. Negative variance is shown as a negative value and % and is colored red.

The inverted variance is calculated using the default formula found here and then the sign is flipped.

There are different options for setting the node lock status. See this article about locking and unlocking nodes.

To change the variance convention, select the option from the drop-down menu:

There are several advanced options that are helpful in specific use cases.

When the Skip Actuals box is checked, a node will ignore the Actual periods and take on values based on the input table in that specific scenario for all time periods, including Actual periods.

When the Forecast inputs box is checked, a node will ignore any inputs in the Actual periods and return values only in Forecast periods. Any inputs with start dates in Actual periods that can impact Forecast periods (i.e. growth rates, repeat every N, etc.) will still return the correct values in the Forecast periods only.

In this example, both nodes have the same input table. Only the second node called "Forecast Only Node" has the Forecast inputs box checked.

When the Sync scenarios box is checked, input values are automatically synced across all scenarios.

When the Allow drill down box is checked, logically related components can be viewed from the table.