I think it is even worse when importing from SSAS. We imported a Calendar table and now we have columns named like [Calendar. Calendar Date], while the full column reference is actually 'Calendar'[Calendar. Calendar Date], at least it is obvious this column comes from the Calendar table :)).
Having the schema name in front of the table takes unnecessary space from the Power BI authoring canvas and makes it difficult to read table names.
Definitely very helpful. Please add.
We would like to use a layer of database views in a "PowerBI" schema to grant users access to our fact and dimension tables. This is a nice way to insulate users from the underlying tables, and simplifies permissions because we simply grant SELECT and VIEW DEFINITION to the PowerBI schema. It would be very useful if we could automatically prevent Power BI Desktop from including the schema name by default.
This is so important. Please consider it. For enterprise clients, we use schemas as a security boundary, and I believe that best practice for Power BI is to separate out the views/procs that Power BI accesses into a separate schema with just SELECT and EXECUTE permission for the account that Power BI connects from. That all gets messed up when every time you import a set of views, etc. it prepends the schema name. That makes us have to rename every single one.