Need -One‑Click Collation Settings for Semantic Models and Lakehouse

Today, changing collation settings such as case‑sensitive or case‑insensitive behavior in Semantic Models and Lakehouse environments is not straightforward. It usually requires using JSON DDL scripts, advanced SQL commands, or backend configuration changes. This makes the process difficult for many users. Business users are unable to manage it on their own, and even technical users often find it complex and error‑prone. Small mistakes can lead to misconfiguration, unexpected query results, or broken relationships. In many cases, customers need to raise support tickets or rely on experts to make these changes, which slows down their work. The experience is also inconsistent across different artifacts. In Lakehouse scenarios, collation behavior is tightly linked to the SQL endpoint, which adds more complexity and confusion. Customers generally expect such a basic and important setting to be available through a simple, guided user interface instead of low‑level scripts and manual steps.

Proposed Solution
Introduce a simple, user‑friendly button in the UI that allows users to control collation behavior without needing scripts or advanced configurations. For Semantic Models or Datasets, add a Collation Mode option under Model Settings. This should be presented as a clear toggle or button where users can switch between Case‑Insensitive and Case‑Sensitive. The button should include brief, helpful text explaining how the selected option affects DAX queries, SQL queries, relationships, and overall performance. This allows users to understand the impact before making the change.
For Lakehouse and SQL Endpoints, add a Collation Configuration button directly in the Lakehouse settings and SQL Endpoint settings. With a single click or toggle, users should be able to choose between Case‑Sensitive and Case‑Insensitive behavior. Once selected, the setting should be applied consistently across tables, metadata, and query execution to ensure predictable and consistent results.
By introducing a simple button or toggle in the UI, customers can manage collation settings confidently and independently. This removes the need for manual scripts, reduces errors, improves consistency across artifacts, and provides a much better overall user experience.