Lakehouse Table schema change does not reflect in Custom Direct Lake semantic model

Hi

I have multiple tables in my Lakehouse. Inside the Lakehouse, I clicked on the "New semantic model" option to create a direct lake semantic model, import the tables and create relationships.

Later, one of the tables required additional columns, so I altered the schema in the Lakehouse to add the additional columns.

After adding these additional columns, the semantic model does not reflect these new additions by default.

I will have to "remove" the table from the model and re-add the table, and only then these new columns are visible in the table.

This is a huge problem, especially when I have to recreate the table relationships all over again given that it is a FACT table.

I have read this blog post from Microsoft: https://powerbi.microsoft.com/en-in/blog/improvements-for-creating-new-direct-lake-semantic-models/ which says that "In custom Direct Lake models, schema changes are not updated automatically without user intervention. This behavior is comparable to import and DirectQuery semantic models in Power BI."

This does not make any sense.

Why should I remove, re-add and create the relationships again just because of schema changes (additional columns) in the table?