Add 'Column' as an option for initial value for parameters

Caroline Blanchard

Parameters are a great way to dynamically create reports for end users, customized to what they expect to see. We are currently working on parameters that bind the viewing users department to automatically filter the report to their own personal department. We've done this successfully for users with only one department, however for users with multiple departments we've run into issues. For example, we've not been able to properly reference the end users 'user name' parameter within the logical SQL Query for the initial value calculation. If we were able to select a custom column for initial value we would be able to properly select what we'd like to see.

In the above picture, you'll notice the available values column has '211' in there which is a user name selected using @parameter("User Name")(NULL) in the case when statement in the custom column calculation. Because its done in the custom calc, it actually inputs the correct value into the parameter. As a work around, for those with only one department if we use 'First Available Value' for the initial value it will properly select the end users department name which we can use for binding to department filter. We would love if column could also be chosen as an initial value for creating a parameter that may have to have multiple selections already in there.

Krishna Prasad Kotti-Oracle

Column for a initial value does not work as it will bring in all the values of the Columns as initial value. This can cause issues and hence not desirable. It is best to use Logical SQL based to restrict the values.

Caroline Blanchard

@Krishna Prasad Kotti-Oracle As stated above, logical SQL does not work when referencing another parameter in the logical SQL.

Caroline Blanchard

@Krishna Prasad Kotti-Oracle Bringing in all the values of the custom column (in this case 4 or 5 values maximum) is exactly what I want it to do.