📢*New Feature: NULL-Safe Joins for Dataset References* We're excited to introduce NULL-Safe Joins for dataset references, allowing rows with missing relationship values on both sides of a join to match instead of being treated as unrelated. What's New? 1. NULL-safe join matching: When enabled, rows with NULL on both sides of a join relationship are treated as matches, unlike standard SQL equality. 2. Configurable at the model level: Use isNullable and nullValue fields on facts, aggregated facts, attributes, labels, and reference sources to control null-handling behavior. 3. Opt-in setting: Enable via Settings > SQL Generation > Null-Safe Joins Key Benefits • Prevents empty attribute values from splitting into multiple rows when they should be grouped together. • Limit potential performance impact to only the queries that require NULL-safe matching • Control join behavior without changing how optional relationships work. 📄*Docs:* Here Have questions or feedback? Drop them below 👇