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

Data Source When Deploying SSRS Report #4

Closed
MarshallPless opened this issue Jul 19, 2018 · 15 comments
Closed

Data Source When Deploying SSRS Report #4

MarshallPless opened this issue Jul 19, 2018 · 15 comments

Comments

@MarshallPless
Copy link

We are deploying SSRS reports and data sources directly from VS. In this the Data Source is being dropped.
I have tried several configuration changes to get the report to recognize the data source.
Is there an entry we can add that will force the location of the Data Source? In your statement below it seems it is defaulting to "DataSource" and our folder name is "Data Source".

Reference DataSources: If selected the DataSources in the configuration file will be referenced in the Reports, by matching the DataSource name.

Thanks!
Marshall

@mmajcica
Copy link
Owner

mmajcica commented Jul 20, 2018

Hi,
Data Sources can be only 'declaratively' specified in the configuration and then they will be created. You can't provide them as artifacts (like rdl files). I think it is mentioned in the description page somewhere.
This is because they are easy to create and if specified in config file it is also easy to manipulate the environment dependent values from within the release.

Does this answer you question?

@MarshallPless
Copy link
Author

MarshallPless commented Jul 20, 2018 via email

@mmajcica
Copy link
Owner

Sure, here you can find one:

https://marketplace.visualstudio.com/items?itemName=mmajcica.deploy-ssrs

<DataSources>
    <DataSource ConnectionString="Data Source={{Server}}\{{Instance}};Initial Catalog=MyDB" Name="MyDB" Extension="SQL" CredentialRetrieval="Integrated" />
    <DataSource ConnectionString="Data Source={{Server}};Initial Catalog=MetaData" Name="MetaData" Extension="SQL" CredentialRetrieval="Store" UserName="user" Password="password" WindowsCredentials="True" />
</DataSources>

@MarshallPless
Copy link
Author

MarshallPless commented Jul 20, 2018 via email

@mmajcica
Copy link
Owner

mmajcica commented Jul 20, 2018

The should match on name.

Check here

$nodes = $Definition.SelectNodes('d:Report/d:DataSources/d:DataSource/d:DataSourceReference/..', $NsMgr)

and here

@MarshallPless
Copy link
Author

MarshallPless commented Jul 20, 2018 via email

@MarshallPless
Copy link
Author

MarshallPless commented Jul 20, 2018 via email

@MarshallPless
Copy link
Author

MarshallPless commented Jul 26, 2018 via email

@mmajcica
Copy link
Owner

Not at all.

It is sure possible what you are asking for.
You can set SecurityPolicy on the following elements:

  • DataSource
  • DataSet
  • Report
  • Folder

It is set in the same way as on folder, just nest it under the desired element, e.g.

<Report Name="Error Report" Hidden="true" FileName="Error Report.rdl">
	<Security>
		<Security Name="Administrator">
		  <Roles>
			<Role>Browser</Role>
			<Role>Content Manager</Role>
		  </Roles>
		</Security>
  </Security>
</Report>

I also tested it after the implementation on Reports, so it should be good to go (I haven't tested DataSets much).

Let me know how it went.

@MarshallPless
Copy link
Author

MarshallPless commented Jul 27, 2018 via email

@mmajcica
Copy link
Owner

It just means that user on which you are running you agent NATLAUTO\NACBUILD1$ doesn't have sufficient rights to deploy that report.

@MarshallPless
Copy link
Author

MarshallPless commented Jul 27, 2018 via email

@mmajcica
Copy link
Owner

Have you perhaps made security on the folder such that the build account has no rights to deploy into it? Can you add on that folder security also the build account with an admin role?

@mmajcica
Copy link
Owner

Also, lets continue via email. Can you drop me your email address via http://blog.majcica.com/contact/ ?

@MarshallPless
Copy link
Author

MarshallPless commented Jul 27, 2018 via email

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