Dataset views: avoiding manual schema updates following changes to backing dataset schema

Hi all,

We have a series of dataset views whose that each utilize a single backing dataset. These backing dataset’s schemas are subject to frequent change. We maintain the backing datasets via incremental append syncs and utilize the option to allow schema changes for the sync / target dataset.

There doesn’t seem to be an option to also configure dataset views to allow for schema changes when they’re built, which prevents these views from building until we manually update their schema in accordance with the changes applied to the backing dataset. We manage a large number of these views, so manual upkeep of their schemas is not ideal.

Is anyone aware of an approach to either programmatically manage dataset view schemas, or otherwise configure them such that they can continue to successfully build without manual intervention following changes to the backing dataset’s schema?