Setting a Report-level default Data Source does not affect new Components, as it should

Per the "Replace the data source for a component, page, or report" documentation,

"Setting a data source at the page or report level has no effect on existing components in your report. Instead, new components that you add use the page or report-level data source by default."

I understand the first part and it works as it is written. But the second part - about new components using the report data source - i just have not found this to be true. The steps I am following:

  1. [Setup] Have two Data Sources, Data Source A and B
  2. Create a new Report, connect to Data Source A (it will create a default component connected to A)
  3. Immediately, go into File > Report settings and change the Data Source to Data Source B
  4. Create a new component via the "Add a Chart >" button (for instance, a table)
  5. If i understand the above, it should be using the Report Data Source, Data Source B. But this is where i see it is still using Data Source A. And changing the Data Source at the Report Level from A to B or vice versa does not do anything. The new components seem to still have local component data source settings rather than using the report default.

I was ultimately trying to get a workflow going where i could have a report built upon a single data source that i could easily go into the data source menu to change from A to B (prod to dev, for instance). I think I will need to find alternative methods that work at the component level (i.e., using Select > Charts with this data source on page) or use the Copy Report UI and use the "New Data Source" selector.

I was excited by the promise of what was written in the documentation, however. Is this functionality working as expected? Did i misinterpret the documentation?

Solved Solved
0 4 537
1 ACCEPTED SOLUTION

I just tested this and it worked exactly as you wanted it to 😕

That is, in step 5, my new chart was connected to Data Source B, even though the first chart was still connected to Data Source A.

Maybe this has something to do with your report, specifically? Is the page level data source set? Does the problem still occur if you use a fresh report, like I did for my test?

 

 

View solution in original post