Best Practices for Adding Columns to a Snowflake View Without Breaking Power BI

Hello sirbaklava 

as far as i know adding a new column to your data source (e.g., a Snowflake view) will not cause existing Power BI reports to fail, as long as the new column does not interfere with the existing schema or logic. Here’s why:

1. Schema Mismatch Handling: Power BI retains the schema of the data source at the time of its initial connection. When you add a new column, Power BI will simply ignore it during refreshes because it is not referenced in the dataset or reports. This means existing queries, measures, and visuals will continue to work without errors.

2. Impact on Existing Logic: Since the new column is not part of any existing queries, measures, or visuals in Power BI, it does not affect the current functionality of your reports. The refresh process will only query the columns that were part of the schema when the dataset was last configured.

Some best practices:

Use `CREATE OR REPLACE` for Snowflake Views

If you want new columns to be part of query

In Power BI’s Query Editor, set the query to dynamically include all columns by using `Columns=null` in the Advanced Editor. This ensures that any new columns added to the source are automatically included during refresh

if this is helpful please accept the answer and give kudos