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

Hi Vincent,   Thank you for the answer regarding a dedicated interface to Denodo.   Our understanding in working with SAS Tech Support and the developers of the ACCESS engines is that bug fixes and other enhancements have been made to the Interface to JDBC that might address some of the issues we are experiencing; however, these updates are only available for Viya 4. As we are currently using SAS 9.4 to connect to Denodo via JDBC, we would at least like to see these enhancements be released for Foundation SAS. Additionally, we have seen several new java-related issues impacting our JDBC connections following an upgrade to SAS 9.4 M8. As this is SAS' latest release of the SAS 9.4 software, we would expect that other products that would be impacted by these changes would also receive hotfixes. What is the best way to request hotfixes for known bugs and/or request that enhancements to the ACCESS Interfaces developed for Viya 4 also be made available for other SAS products?   Thanks, Corey ... View more

Hi Vincent,   Thank you for your reply. I have looked at the link you shared, and it appears to be a README with documentation about how to configure the JDBC interface in SAS Viya, code to define libraries in SAS Viya, and a brief table of the results of some smoke testing. The links included in the table to the actual tasks must be behind a firewall because I am not able to open them.   I'm not sure how this addresses the concerns I raised. To start, our issue is with connecting SAS 9.4 to Denodo via JDBC, and the seemingly countless small incompatibilities that arise from having to use a generic connector. Everything in the github link is for SAS Viya, not SAS 9.4, though it is not clear which version of SAS Viya was used for the smoke testing.   Even if we disregard the fact that these tests were run on a different platform, I do not think performing smoke testing addresses our concerns. I found the jdbcSmokeTesting_template.sasnb file elsewhere in the repository, which I assume is reflective of the tests run against Denodo. As this file clearly states, "A smoke test is a quick and simple test that verifies that the basic functionality of the connection is working as expected." Looking further at this file, the smoke testing appears to run some very basic commands (e.g., create table mylib.class2 as select * from mylib.class;). I am not surprised to see that the basic tasks included in the smoke testing performed as expected. The issues we are experiencing are considerably more complex than what might be surfaced by running a simple select * on a single demo table of dummy data.   Our request or suggestion is for a custom connector to be developed for connections to Denodo - one that would be compatible with the products we already license from SAS, SAS 9.4 and Viya 3.5. It has been disappointing to see that despite having upgraded to M8, SAS' most up-to-date version of this platform technology, our issues persist. In fact, we discovered several new issues were introduced with the upgrade to M8 due to changes with Java. Additionally, while we would prefer that a custom connector be built to address the many small opportunities for optimization that a custom connector would offer, we would also be encouraged to see enhancements and bug fixes developed for the JDBC interface to address known issues. We have heard in past troubleshooting sessions with SAS support and the developers of the ACCESS interfaces that recent enhancements have been made to the ACCESS Interface to JDBC; however, none of these enhancements or bug fixes are available to us as they are only available for Viya 4.   ... View more