You can translate the question and the replies:

Propagating new columns from Base View till Final View

Hi, I have a situation where few new fields were added in the DB from which i created base view (BV1). Now when i click on source refresh, those new fields appear in BV1 but they are not propogating to interface view and any other dervied (selection) view created based on that interface view (IV1). following is the structure i am using - BV1 > DV1 > IV1 > DV2 > DVfinal I can see the change till DV1, also i have tested this where all views are in same VDB and another case where from IV1 onwards the VDB is diferent from BV1. Thanks for your response in advance
Base view
user
14-10-2022 08:45:17 -0400
code

3 Answers

Hi, When the modifications in the base view affect other views, the Administration Tool will display a dialog with a list of the affected views. You can select which views you want to propagate these changes, by selecting the check boxes that appear on the right-end side (scroll right) before each view’s names (select the header’s check box to select all the views in the list). Also, you can refer to the [Source Refresh](https://community.denodo.com/docs/html/browse/latest/en/vdp/administration/creating_data_sources_and_base_views/source_refresh/source_refresh) pages of the User Manuals for more information about Source Refresh. Hope this helps!
Denodo Team
17-10-2022 04:37:53 -0400
code
Thanks for the reply. but like i said the changes are propogating till BV1 > DV1 only. from Interface (IV1) onwards i have to add new fields manually. The admin tool shows me the affected views but changes are not being reflected in them. My expectation was since there's a change in BV1 all the views related to it (multiple types) will automatically gets reflected, whihc is not the case.
user
17-10-2022 05:15:16 -0400
Hi, I understand that you want to propagate new fields from DV1 to IV1. Unfortunately, it is not possible to do it from other views to the interface view because the interface view is not designed to accept schema changes from other views. For example, one of the main use cases of interface view is “Data model abstraction”. It is useful when a project migrates the underlying data stores to the cloud but you want to make sure the view schema does not change. You can refer to the [Creating Interface Views](https://community.denodo.com/docs/html/browse/8.0/en/vdp/administration/creating_derived_views/creating_interface_views/creating_interface_views) page of the User Manuals for more information about interface view. Hope this helps!
Denodo Team
25-10-2022 04:11:52 -0400
code
You must sign in to add an answer. If you do not have an account, you can register here