Applies to: 
Kyvos Enterprise Kyvos Cloud (SaaS on AWS) Kyvos AWS Marketplace
...
Resilient semantic model process with (table metadata) changes over time
There are time when metadata changes in different datasets are requires. Following are the scenarios which might occur and possible solutions ensure the semantic model doesn't fail.
Column got added in table (at the end) - Dataset SQL has list of column names in "Select"
No changes required and process will not have impact
Column got added in table (in-between) - Dataset SQL has list of column names in "Select"
No changes required and process will not have impact
Column got added in table (at the end) - Dataset SQL has "Select *"
No changes required and process will not have impact
Column got added in table (in-between) - Dataset SQL has "Select *"
Refresh and save the dataset again. Data type or format changes will not be overwritten when saving the refreshed metadata.
Column got deleted in table
Column used in semantic model
Refresh dataset and Relationship design and save. Remove that attribute from the semantic model design, and perform an incremental process. That deleted column will become irrelevant and wont be available for querying.
Column not used in semantic model
Refresh dataset and save.
Dataset SQL has "" as IsAdjusted and processses are done
Column got added in table (Same position as of dataset or different position) -
Remove that column from Dataset SQL (tds-service incremental query needs to be updated), refresh and save dataset/Relationship design. semantic model reprocess won't be required.
If data type is changed of column in table used in semantic model
For example, for an existing integer column data type is changed to string then dataset will start giving warning but process will only fail in case Kyvos receive string value in that column instead of integer otherwise process won't fail.