Configure Multi-Select Actions in a OneStream Grid View
A OneStream Grid View can turn several selected rows into one controlled action. The pattern works by binding the chosen column to an input parameter that the button passes to a Dashboard Extender rule.
Before configuring the action, confirm which column uniquely identifies each record and what should happen when no rows are selected. This prevents ambiguous values and simplifies testing.
The Use Case:
You want to have your users be able to select multiple items from a Grid View on a dashboard and have those multiple selections drive an action. In other words, the ability for the users to select multiple items from a Grid View and have those selections passed to a Business Rule.
The Solution:
1. Create a Grid View and set the “Allow Multiselect” property to “True”.
2. Set the “Column Name for Bound Parameter” to the column name that will be used to pass the selections to your business rule. In this example, the selected PersonID column is passed to a business rule.
3. Create an input parameter. This parameter will be bound to the grid view and will contain the selected values from the grid view.
4. Set the Bound Parameter property of your Grid View to this parameter.
5. Create a button. This button will execute a Dashboard Extender Business Rule and will get the selected values from the grid view.
6. Notice in the name value pairs that are being passed to the dashboard extender that the parameter is enclosed in square brackets. The square brackets are important, otherwise the selected members that are passed as a comma delimited string will not be interpreted correctly.
7. In the Dashboard Extender, create a string that will hold the passed-in selections as a name value pair. In this example, nothing else happens in the business rule other than writing the selected values to the error log for demonstration purposes.
8. From the dashboard that contains the button and the grid view, select a couple of rows and click the button.
9. The selected PersonID values are then written to the error log.
Keep in mind that the business rule in this example is very basic for demonstration purposes. The sky is the limit as to what you can do with those values now that you have them in your business rule. In addition, this will also work for a SQL Table Editor.
OneStream Grid View Best Practices
Test the OneStream Grid View with one row, several rows, and no selection. Confirm that the parameter preserves the expected delimiter and that every identifier reaches the rule intact.
Validate permissions before executing updates. The interface may hide or show a button, but the business rule should also confirm that the user is authorized for the requested operation.
Use clear names for the bound column, parameter, and name-value pair. Document the required brackets and log enough context to diagnose unexpected values without exposing sensitive data.
After publishing, retest the OneStream Grid View with realistic data and a non-administrator profile. Also verify the SQL Table Editor behavior when reusing the same pattern.
Record the expected and observed results so future releases can be checked against the same functional acceptance criteria.
Extend this configuration with create a non-administrator user, configure a dashboard pop-up button, add a help-file button, control data input with a business rule, learn what OneStream is. Also review the official OneStream documentation to validate syntax and capabilities for your release.
Contact
MindStream Analytics
Want to learn more about OneStream Software? Please complete the form below and we’ll get back to you shortly.
