on
RE:
I agree with everyone else here - please fix this. It is making self service BI impossible
RE:
This would be most helpful for our retail customers. We have a customer who needs to be able to see stock level in each location ASAP using the inventory lookup in POS. Since other POS store inventory functionalities can be performed by selecting a specific location such as Stock count and Inventory adjustment today, it makes sense to have this prioritized. Looking forward to hearing more from you regarding this!
RE:
From the last 6 years this idea was not picked up even though enough votes are there
RE:
This would be useful for us too. It's baffling that English (UK) is not supported by PowerBI Service, and that this can impact the integrity of the data I distribute to the business.
RE:
There's a new slicer value option, but it doesn't contain an option for drop down. There's also a border option which doesn't seem to work (no idea what it actually does do).
RE:
Here's the reference documenting that "identifiers are case-insensitive" in Spark SQL, which ought to be a guide for Fabric as well: https://spark.apache.org/docs/latest/sql-ref-identifier.htmlFurther, SQL Server's default behavior in the US is to treat SQL identifiers as case-insensitive: SQL_Latin1_General_CP1_CI_AS. https://learn.microsoft.com/en-us/sql/relational-databases/collations/set-or-change-the-server-collation
RE:
If we want any level of consistency in the behavior, we should look the Spark SQL standard, which says "identifiers are case-insensitive". Having collation options would be a plus, but at a minimum we should stick with standards as the default.