Custom SQL is used to provide special SQL syntax that the software does not generate. In the absence of row‑level security, users with proper permissions for theInteractive Reporting document can modify custom SQL to produce ad hoc results.
When row‑level security is in place, Custom SQL is affected in two ways:
If the published Interactive Reporting document contains an open Custom SQL window, it is used as is when the user processes a query. No restrictions are applied to the SQL. However, the user cannot modify the SQL. While this can be a handy feature, care should be taken when publishing Interactive Reporting documents that require custom SQL that they don’t compromise the security requirements.
If the user chooses the Reset button on the Custom SQL window, the SQL shown includes the data restrictions, and the original intent of the Custom SQL is lost and the user will not be able to get it back except by requesting the Interactive Reporting document from the server again.