Forum Discussion
Switch underlying table to a complete report page
Hi,
Is there any way to just change the specific underlying table to a report page or visualization on a report page?
Assume you have built a page which consists of a great number of fields from "Table x". After that, you have duplicated that table (named "Table y") and it will thus have ALL the existing fields available as the old, original, one. I want to be able to just "switch" in the report or visualization on a report page from Table x to Table y WITHOUT having to drag&drop all fields one-by-one.
Any efficient move to make? :)
Br/Henrik
Hey,
maybe this would work also in your case ...
I sometimes work against a database schema that evolves. I started working against a table called smallertable
Than on notice of the team I swith the underlying table in the QueryEditor: from smallertable to smalltable just by editing the string in the navigation step
For me this works great ...
So maybe you should not looking to change the link from the visual to its underlying tabel, but to change the content of the used table editing the source.
For this reason we often use this approach:
- create a query called wktable
- create a reference to the table wktable and call it goodtable or something similar
- for the model and hence for all our reports and dashboards we use the table "goodtable" (from a performance point of view this would not work as well in Excel, because there are some issues with caching of the referenced queries)
So we are free to change the source of goodtable to wktable2 or wktable3
Hope this gets you started
1 Reply
- TomMartens
Super User
Hey,
maybe this would work also in your case ...
I sometimes work against a database schema that evolves. I started working against a table called smallertable
Than on notice of the team I swith the underlying table in the QueryEditor: from smallertable to smalltable just by editing the string in the navigation step
For me this works great ...
So maybe you should not looking to change the link from the visual to its underlying tabel, but to change the content of the used table editing the source.
For this reason we often use this approach:
- create a query called wktable
- create a reference to the table wktable and call it goodtable or something similar
- for the model and hence for all our reports and dashboards we use the table "goodtable" (from a performance point of view this would not work as well in Excel, because there are some issues with caching of the referenced queries)
So we are free to change the source of goodtable to wktable2 or wktable3
Hope this gets you started