v1.10.0

[gowthamrajj]

Changes

• Exclude specific portal partition columns. exclude_portal_partition_columns now accepts an array of column names, not just the boolean, so a model or CTE can drop any subset of its monthly / daily / hourly partition grains instead of all-or-nothing. Set it in the .model.json, the model wizard's Exclude Partition Columns picker, or the CTE side-panel; an array overrides exclude_framework_artifacts at the same scope.
• Framework-artifact excludes now in the model wizard, with guidance. The Additional Fields → Column Excludes step surfaces the full set of opt-outs — datetime, portal source count, partition columns, and the date / daily WHERE filters — each with a tooltip on when it's safe to drop and how it affects query cost. The CTE side-panel's exclude controls gain the same tooltips.
• Warns when a bulk exclude can't drop a framework column. Naming datetime, a portal_partition_* grain, or portal_source_count in an all_from_model / dims_from_model (or CTE) exclude raises a Problems-tab warning pointing to the matching flag (exclude_datetime, exclude_portal_partition_columns, exclude_portal_source_count), since the framework re-injects those columns and the bulk exclude alone has no effect. Re-adding the column as a named select in the same list — the replace pattern for re-graining datetime — is recognized and does not warn.

[arunxdev]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.