Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reference DataSource Issue #40

Open
acds opened this issue Dec 31, 2019 · 1 comment
Open

Reference DataSource Issue #40

acds opened this issue Dec 31, 2019 · 1 comment

Comments

@acds
Copy link

acds commented Dec 31, 2019

Hi @mmajcica - Thanks again for supporting this Azure DevOps task!

I have "Reference DataSource" turned on - but this is not working as expected.

To confirm expected behavior - If a report names a data source

<DataSources>
   <DataSource Name="MY-DATA-SOURCE">
     <DataSourceReference>/DEV/DataSources/MY-DATA-SOURCE</DataSourceReference>
     <rd:DataSourceID>b854d181-2e6c-42f2-9a2d-39804cb15d55</rd:DataSourceID>
   </DataSource>
 </DataSources>

or say

<DataSources>
    <DataSource Name="MY-DATA-SOURCE">
      <DataSourceReference>MY-DATA-SOURCE</DataSourceReference>
      <rd:DataSourceID>104a6a0e-afa9-451d-83a2-93a974ef068c</rd:DataSourceID>
    </DataSource>
  </DataSources>

I have "No" DataSources defined in the DeployConfig.json. We'd prefer not to need expose or the DataSource configuration (and credential) in the Deploy Config, as these are set up and maintained separately.

Is it correct to have the expectation that given an RDL referencing a DataSource name (in my case (MY-DATA-SOURCE) that the task will find the most local DataSource of that name and match that DataSource into the RDL/Report as its deployed to that data source ?

Also to confirm, is the best approach is to have each RDL configured as the second example above ?

We obviously can't manage the <rd:DataSourceID> between environments - and that is what the "Reference DataSource" is supposed to achieve?

What are we otherwise missing ?

@vferris
Copy link

vferris commented Jun 14, 2021

@acds Did you find an answer to this? I'm having an issue where the reports appear to be correctly linked in the web ui, but none will accept passed parameters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants