Preset Feature Feedback
What is the problem or goal you're trying to solve or accomplish?
DAR (Data Access Role) matching in Preset is case-sensitive for catalog and schema names. When datasets are created with inconsistent casing, each variation generates a separate DAR entry. This causes permission gaps where users lose access to dashboards because their DAR is configured for one casing pattern but the dataset references another.
How are you solving it currently?
Admins must manually add a DAR entry for every naming variation (uppercase, lowercase, with/without catalog). This is error-prone, creates DAR clutter, and is hard to maintain as more datasets are created.
What is your recommended solution?
Make DAR matching case-insensitive for catalog and schema names, so that DATABASE_NAME and database_name are treated as the same resource when evaluating permissions. This would eliminate the need for duplicate DARs and make the permission system more resilient to naming inconsistencies.
