Forms Best Practice

Introduction

Forms are an integral part of any Kepion Application. They are used within Dashboard Apps and can be used to create visualizations within Kepion or Power BI. In order to ensure that other parts of the application are running cleanly, it is important to improve the performance of the Forms where possible. Below are some options that you should take into consideration.

Best Practices

Default Filter Members

You should always default each filter selection to the lowest member within a hierarchy to give better performance when a Form is first opened.

Use SQL Over MDX

When possible use SQL scripts over MDX scripts. This will help improve the performance of both your Form and your application.

Cell Attributes

It is considered best practice to add Cell Attributes whenever you need dynamic formatting that will affect  the Dimension Members on a Form. Cell Attributes are also used to validate input and override certain properties of a cell.

Static Cell Formatting

If there is formatting you need that is not dynamic, it is recommended you do the formatting by rows and or columns because it will decrease the overall Form size. For example, if you want to add a splash of color to your Form, you can highlight the row, and select your color of choice.

Hide Empty Rows and Columns

Turn on the Hide Empty Rows and Columns options. This shrinks the size of the Form to just where there is data.

Keep Form Design Simple

Limit the number of Dimensions on the rows or columns. Limit the scope and size of the Form. Shrink large Forms down with more filters. Disable any features that aren't necessary, or redesign the Form in a way that doesn't need them (annotations, drop-downs, cell attributes, increase/decrease colors).

Use Multiple Forms

Break large Forms into multiple smaller Forms, and place them side-by-side on a Dashboard.

Valid Relationships

Build validation models and define relationships between Dimension Members, to limit how many actually need to exist on the Form.