Planning Form Behavior in Smart View

Forms behave differently in Oracle Smart View for Office than they do in Planning.

Attributes in Planning forms are not displayed in Smart View.
Multiple levels in an outline are displayed differently in Smart View than pages on the Planning Web application. Smart View displays up to four levels, while the Web application displays up to two levels.
If a Planning administrator hides a dimension in the row axis of a Planning form, this dimension does not display in the row header of the form in Smart View.
If a Planning administrator has set up a form to use formatting from Planning, and not from Smart View, then no Smart View formatting options (from the Options dialog, Formatting tab) will be applied. This is true whether the Use Cell Styles or Use Excel Formatting option is selected in Smart View.
In composite forms, sections that display as charts in the Planning web application will display as grids in Smart View.
In Planning forms, the handling of decimal place settings between Excel, Smart View, and Planning may, at times, cause rounding issues in submitted data. This can occur even when the decimal precision is set to two decimal places in both Excel and Planning. For example, in a Planning form, you may enter 68.68, but Smart View sends the data to Planning as 68.67999999999, instead of 68.68.
If row drop-down menus are enabled on a form, then Smart Push (which pushes data from different cubes into one form) cannot be used.
Smart View does not support the use of dynamic members, or "members on-the-fly." Dynamic members can only be used in forms in the Planning web application.
When you create a formula on members that calculates the value for a Summary Time Period and then you modify the data for the Summary Time Period member, sometimes Smart View considers that cell to be a dirty cell.
In Smart View, the display order of business rules attached to a form differs from the display order in Planning.
When two forms are on two separate worksheets, the rule variable on the first form changes to the default value after refreshing the page dimension on the second form. This may cause the business rule to invoke an incorrect value for a runtime prompt variable. If this happens, display the runtime prompt to see its value before submitting the rule for execution.
In Smart View, the currency symbol in a cell is displayed differently from the Planning web interface when the Planning option, "Allow multiple currencies per entity," is set to true.
Indentation of dimensions in a Planning form is displayed incorrectly.

Note:

If you are unfamiliar with Oracle Planning and Budgeting Cloud, see the Oracle Planning and Budgeting Cloud documentation and videos available on the Oracle Help Center.