Form Design Considerations

Forms and Cubes

When you create a form, you associate it with a cube, which determines the form's valid members. For example, if you assign a form to the Revenue cube, you can add only accounts that are valid for the Revenue cube. Entered data is saved to the selected cube's database.

Note:

• You can't change a form’s cube after assigning it.

• You can edit form accounts only if their source cube matches the form's cube.

• If you add an account to a form associated with a cube other than the account’s source cube, the account is read-only on that form.

Forms and Permissions

Assign permissions to a form to determine which users can modify its design (for example, layout and instructions) and input data. Users can edit forms only if they have permission to one secured dimension’s member. For example, if users have read-only permission to the Europe entity, the rows and columns that include the Europe entity are read-only. Users can change data only for members to which they have write permission.

Forms and Versions

For bottom-up versions, rows and columns with level 0 members allow data entry. Rows or columns set to a parent member are read-only. The point of view must also be set to the level 0 member to allow data entry on a bottom-up version. Target versions allow data entry in parent and children members.

Filtering Form Members by Attributes

You can select members by using attributes. For example, on the Entity dimension you can select members by a specific Region such as South. The resulting grid will only contain members that have the South attribute (for example, TX, NM, and so on). Values can be entered and saved into rows and columns filtered by attributes.

Forms and Shared Members

Because you can't select shared members individually, select them using a relationship function. For example, select an alternate functional rollup to include all members under that rollup. Users can enter values in rows or columns that display shared members, and data is saved to the base members in the database.

Forms and Calculations

To optimize calculations, select row members using relationships (such as Descendants or Children) instead of selecting individual children. For example, calculating individual parent-level totals could take several passes, so use a relationship instead.