I'm trying to deploy a report from SpagoBIStudio 5.2.0 on a SpagoBI Server v5.1.0.
The report works perfectly in SpagoBIStudio (locally in my computer), and I successfully created the data source and the data sets using the web interface of SpagoBI Server.
Nevertheless when I click on the "Deploy" option of my ".rptdesign" file, I see the following dialog and the "Finish" button is always disabled.
For some reason I can select the correct Datasource but the Dataset dropdown list is empty and disabled. I guess this could be the problem.
The data source is a JDBC-Hive connection to Cosmos and the Datasets are defined as HQL queries in both Studio and Server.
Does anybody know why the datasets aren't listed in the deploy document wizard of SpagoBIStudio?
Thanks in advance.
you cannot finish the deploy not because of dataset but because you did not select any functionality on the tree on the right.
You don't have any functionality on server where to store your document, so you should go to server with and administrator user role,
then with the menu on the right, on the profile section, select the "functionalities management" menu and create a folder that is child of the root. Give it the permissions you need
After this operation try again the deploy and you should be able to select one funcitonality and so have finish button enabled
greetings
the dataset selection is disabled because a Birt Report is not linked to dataset that way.
There are two ways of using datasets in Birt:
- Birt embedded datasets, that can be of several types provided by Birt (SpagoBI has no role with that)
- SpagoBIServer type dataset; these are linked to SpagoBIDataset by providing label, but this association is written inside template, during template definition.
Hope this fix your problem, I would suggest you also to take a look at SpagoBI wiki page for further informations
greetings
Giulio
You don't have to select the dataset. Your finish button is not enabled because you haven't select the path from the functionalities tab. After selecting it will be enabled and your report will be deployed. After deployment you need to create Analytical drivers for the parameters through which your report will run.
NOTE: You must have a Active server configured under resources under SpagoBI project folder.
Related
Do not seem to be able to find any place in the portal or Report Builder where I can actually edit the connect string & creds.
Report Manager shows the XML, but that really is it.
Disk files (from the looks of it) are no longer present in high versions (using SQL 2016/2017).
Is there a known location anywhere in GUI, or maybe direct edits in the SQL Server repository?
I can't even delete a shared source anymore, only view or test the connection.
If anybody could post a screenshot, it'll be highly appreciated.
EDIT: Just found out - when I create a new Data Source, it's editable; the imported data sources are not.
There are two ways of doing this. You can set the 'overwrite datasource' option in the project properties.
Or, you can got to the report portal , show hidden items in the view menu and there is a folder called "data sources". Open this and you will see all data sources, from there you can edit and save changes. All reports that use that datasource will be affected.
I got a report with 2 data sources and both are Shared Data source. I am trying to change both of them to Custom Data Source but when I re-upload the report in my Report Manager, it won't work.
Edit: I don't have an error because the report successfully uploads, but the data source doesn't change. If I have a field in the report, the report shows the new field, but the data source stays the same.
This might be because of caching that SSRS does with the datasource for the report on the server. Do the new datasources have the same name as the old ones?
You could create the custom datasources in the DataSources tab in the Manage menu for the report in the report manager.
To do this open up the Report Menu by click on the "..." then selecting Manage
Then click on the Data Sources Tab, then change the data source to Custom Datasource.
Then set up the datasource like you did in the report, you will need to select SQL Server for the Connection, add the connection string and choose the authentication type which in the image below is windows authentication but I am not sure how it is set up on your server. Then click Test Connection. Then Click Save (make sure you click Save before navigating away).
Or you could delete the old report in the report manager and then upload it again. Note that deleting the report will delete any schedules and other customization you have done ie. Name and Description.
Is there an error message? It won't work could be a bunch of things. I'd upload a picture of the error or whatever screen you can't get past. Let me know when you can do that, then it will be easier to troubleshoot. If you can't upload an image than I would:
Check your datasource connections are correct.
Check your datasets are using the correct connection.
This is a setting thats controlled from the deployment properties of the visual studio SSRS project. Right click the project name and select Properties. Then from the Property section of the general page notice "Overwrite Datasets" & "Overwrite Datasources". Change the one that's necessary and re-deploy to see it updated in the report portal.
I'm beginner in hybris. I need to create a jasper reports, using flexible search and mysql server. But I can only use the sql query statement without flexible search in report file (Jrxml source file (.jrxml)).
How can I using the flexible search with mysql?
Are you following the guide provided in Hybris Help for building a custom report? It can be found at https://help.hybris.com/6.3.0/hcd/8b6e40ee86691014b99eda29aebc9d84.html
In the interest of having a source of information in case the link ever becomes dead:
Go to ${HYBRIS_DIR}/hybris/bin/platform
setantenv.bat for Windows or . ./setantenv.sh for Unix/Linux
Go to ${HYBRIS_DIR}/hybris/bin/ext-platform-optional/virtualjdbc
Run the ant command ant dist
Go to ${HYBRIS_DIR}/hybris/temp/hybris/virtualjdbc. You should have two files that have been generated here, hybris-virtualjdbc.jar and vjdbc.jar
You now need to copy these two files to ${HYBRIS_DIR}/hybris/bin/ext-platform-optional/virtualjdbc/lib
Download the Jaspersoft Studio Tool at http://community.jaspersoft.com/project/jaspersoft-studio
Install and Open Jaspersoft Studio
Go to Tools > Options > iReport > Classpath
Click Add JAR twice, each time selecting one of the newly copied JAR files (hybris-virtualjdbc.jar and vjdbc.jar)
Click OK
You now need to setup the Data Source, to do this:
Click on the Report Datasource icon ()
In the newly opened window, click New
Select Database JDBC Connection and click Next
On the next screen you may provide any name for your JDBC Connection
In the JDBC Driver field, make sure you type de.hybris.vjdbc.VirtualDriver
In the JDBC URL field, make sure you type jdbc:hybris:sql:http:///virtualjdbc/service, where is the location of your application server (e.g. https://localhost:9002). Remember this will change with each environment!
Provide a Hybris User for the Username and Password. It may be worth using the admin user to begin with, but make sure you lock it down at a later stage to a user with less access, such as vjdbcReportsUser
Test the connection. Remember you will need the server up and running to be able to use vjdbc
From here onwards, you should be able to create a report using Flexible Search style syntax!
I've created a new SSRS project, and added a shared data source. When I run the project, I get the expected result succesfully.
However, when I try to deploy the report I get:
Error: Cannot deploy the report because the shared data source '/Data Sources/DataSource1' that the report references does not exist on the report server.
I'm guessing I am missing something very simple and critical because I am a complete beginner.
What am I doing wrong?
First, deploy the data source:
Then, deploy any necessary shared datasets:
Now, you'll be able to deploy or run your report.
If trying to deploy dataset but still getting this error...
I have discovered that if you change the name of the shared data source after you have already created a corresponding shared dataset, then the "DataSourceReference" property in the dataset does not change accordingly, is not be editable via the wizard, and it will throw this misleading error.
On the shared dataset, right-click and go to "Open With..." --> "XML (Text) Editor".
There you will see the raw configuration file. Make sure the <DataSourceReference> node has the proper value...
Scenario: You've decided to use a Shared Dataset on your report but you haven't used it. Make sure to select the proper datasets for this issue.
Answer with steps:
On the Report Data tab on your SSDT double click the Datasets(not the one with the folder sign). It'll open the Dataset Properties.
- when the Dataset properties is open make sure to select a Dataset that your report is suppose to use.
-press OK.
-Solved]1
I am using SSRS 2008 R2 and Report Builder 3.0. I set up a shared data source via the browser (http://myserver/reports/) wherein the "credentials are stored securely in the report server" to use with multiple reports. Testing the connection via the browser works.
Now, I fire up Report Builder 3.0. I start a new report and "Add Data Source". I select the "Use a shared connection", browse to the server, and select the above data source. Click "Test Connection" and all is well.
I then try to "Add Dataset". In the dialog, I select "Use a dataset embedded in my report", I select my data source added above, type in the SQL string and click OK. The "Enter Data Source Credentials" appears. No matter what permutation of valid domain (like the domain admin account and others) or SQL Server (like the 'sa' account) credentials plus checkboxes I use, I get an "Unable to connect to data source".
Security settings on the shared data source allow BUILTIN\administrators and domain\administrator all roles. The data source does work, as some legacy migrated reports run fine. Report Builder says the data source connects okay. But, I cannot create new reports, nor modify existing ones.
Any suggestions?
After much gnashing and wailing seems like Report Builder uses information in definitions in Report Server to then run queries locally by itself, and not through Reporting Services.
My mistaken belief was that when I did something like Refresh Fields when setting up a Dataset, Report Builder was going through Report Services to get the relevant output and/or metadata. This seems to not be the case.
I had defined the connection string of the shared data source as Data Source=(local);Initial Catalog=<database name>. Now, this works when you are in Reporting Services' browser interface, but Report Builder seems to read the connection string and use it for itself. Reporting Services on my local development machine does not have any of the setup on the target server running these reports, so anything I would use will fail.
Changing the connection string to Data Source=<server name>;Initial Catalog=<database name>, instead of localhost, allowed Report Builder to work properly. (RB still popped up "Enter Data Source Credentials". I used my Windows credentials, which is a valid login on the target server.)
To accomplish what you are attempting, it sounds like you will need to use windows integrated security.
According to MSDN stored credentials are not passed to client applications. They are for use only by the report server for things like scheduled reports.
http://msdn.microsoft.com/en-us/library/ms159736.aspx
I can tell you that the prompt "Enter Data Source Credentials" is looking for SQL authentication, not domain accounts.
Outstanding question and answer. I really appreciate your careful description. I had the same problem. In my case the problem was that I was accessing Report Builder from a machine connected to my home office by VPN. I guess because I was outside of the Windows network of the home office, RB couldn't authenticate me. Working with a Remote Desktop connected to a machine at the office allowed me to side-step the problem. Your and #RichShealer's answers reminded me that when running the reports from the browser, they're being served up by an inside server machine. This is not the case when running RB, a desktop app.