Realizing that this post was from several years ago, I was recently encountering a similar issue and wanted to share the solution I discovered in case it could be helpful to others who stumble upon the thread. Our Problem: In our case, we were similarly using a dropdown report-level filter (required set to true) to set a parameter value. We were also applying row-level security to the table from which the dropdown options are populated. The impact is that for most users of the report, the dropdown list would filter to a single option. For those with access to multiple options, it should default to the first option available (sorted alphabetically in the dropdown). The issue we encountered is that the default parameter value was set by default to the first value in the complete list of options, as the admin user that created the report had access to all options. Users who did not have access to this first option would correctly have their dropdown list filtered by the row-level security, but even clicking within the dropdown would not override the default parameter. I should also note that the problematic behavior was usually seen when the SAS Visual Analytics report was embedded in another site. Often the report would function correctly when the user viewed the report directly in Visual Analytics running on the Viya 3.5 platform web interface. The Solution: The "current value" of the parameter needs to be empty when the report is saved. This way, the default behavior at report load will be to return the appropriately filtered data in the table, automatically select the first available option in the dropdown (based on user's access), and then set the parameter to this value. From there, the user can select from the dropdown options available, and the parameter value will be updated accordingly.
... View more
