Guidelines for data entry views
Customizations performed on data entry views are the source of most operational problems associated with views. These views require the most customization, due to differing application needs. Certain guidelines must be followed in order to insure proper operation of the underlying components.
Nested dimensions vs. dimension groups
Nested dimensions are supported and recommended for data entry views. When configuring views with nested dimensions, it is possible to inadvertently create a view that results in an extremely large slice of data being loaded. This adversely affects performance of writeback, retrieval, and local consolidation operations. Trim down the allowed members in each dimension of the view in order to limit what appears on the grid to what is minimally required.
Dimension groups are also supported for data entry views. You can create a view in that has dimension groups instead of nested dimensions.
Across and down dimensions
The dimensions listed in the Data Entry views table for across or down the grid are recommendations. The data entry view can have any dimension across or down.
Calculated members added to a grid
Calculated members should not be added to data entry views.
Lines from multiple schedules on a view
Data entry views should not contain lines from multiple schedules when the Submit Data option is present. Submit Data automatically launches a local consolidation process to calculate formulas and downfoots for the schedule associated with the data entry view. Submit Data's local consolidation calculates a single schedule which is determined by the last account on the data entry page.
Local consolidation
When running a local consolidation from a data entry page, the off-grid setting for the Accumulation method dimension is taken into account. If the off-grid dimension is set to Periodic, only periodic data is calculated. If the off-grid member is Year-to-date, year-to-date data is also calculated.