Ioanna,
I see clearly the scenario you are depicting. Unfortunately, once a Data Plan has been saved and established it expects to be served with the same schema for each run. The data sources and content can be dissimilar, as long as the schema matches the original data source.
As transformations are associated with a Data Plan, the transformations are working against specific columns/data types. When your view undergoes schema change, any transformations that worked directly against a "now-gone" column would be come invalidated. This may invalidate one transformation and have a cascading effect through others.
Answering your question directly; structural changes made in the schema of your view would require intervention on your part.
Quick thought: most difficulties occur when your view has dropped a column and a transformations in your Data Plan performs actions on that dropped column. Conversely, If your view added a column, the Data Plan does not worry quite so much because the new column has no association with transformations in your Data Plan.
Regards,
Daniel
Daniel Paner
Principal Product Manager
SAS Viya Data Management
... View more