Does anyone know if it's possible to switch the data set which is used by a Mobile Report? As far as I can see, the only way of doing this would be to add the new dataset and then re-map everything, including filtering to the new one.
It seems a very inefficient way of doing things. In addition, if the original dataset is deleted, there is no way of getting back into the Mobile report!
Any advice appreciated.
In the Report Portal you can manage the settings of the Mobile Report just like you would with paginated reports. You can set the dataset that it's pointing to there without editing the report. As you might suspect, the field names should be the same or it won't know which ones to use.
Related
If I design a report based on some data source, lets say an spreadsheet from google sheets.
but then I want to reuse this report on a different sheet, can I do this without actually editing the report? Can I specify the source somehow in the URL?
Then all I need to do to reuse the report is upload new sheets to my google drive and then connect them to the report by specifying them in the URL.
Is this possible? Or is there a better way to do it?
(I'm googling, but I cannot find out how to reuse reports without actually manually editing them).
so there does seem to be something called "Custom JSON/CSV/XML" by Supermetrics.
and you seem to be able to specify the url as a parameter somehow. If someone has done this and succeeded/failed, or knows of a walkthrough/tutorial, or a variation on this theme then that would be helpful.
Using default connectors, you can't change the Data Source using parameters.
You may try to create a community connector with a parameter to set the desired resource, but I don't think it will fit your needs or worth the effort (you'll still need to edit the report to change the parameter).
However, when you click to copy/duplicate a report, it prompt you to select new sources for each Data Source in your report. It will copy-then-edit your report anyway, but it is a friendly interface. Maybe you should try this.
I'm learning how to use Microsoft SQL server report builder 3.0. I know there is a function in the report called autorefresh. It works when I simply run the report within the report builder. I'm thinking can it still be refreshed after the report is exported.
Another question may related to this autorefresh functionality. When I add dataset into report builder, does it actually load the data into report builder or set up a link between report builder and database? If it sets up a link does that mean when I change something in database, it will reflect on my report builder after I refresh it.
All I want to do is keep the report up to date even after I export it.
Really keen to know the answer.
Thanks in advance.
Make properties visible(View Tab > Check Box View)
Then navigate to report properties(Click on blue space around page). It should say Report in bold at the top of properties.
Expand the Other list and AutoRefresh is the first one.
It's by default set to 0. It's measured in seconds so changing it to 30 will make your report refresh every 30 seconds.
Just so you know, you'll find that even though reportBuilder is the new SSRS(BIDS), it's still very, very similar. So don't feel like you need to always only look at Report Builder only. SSRS tutorials and other facts will be either identical or similar enough to figure it out.
I have a report in Devexpress that is assigned to a certain Datasource and I need to change it to a different Datasource. I want to do this without having to put all the fields back into the report. To help me with this I copied all of my tables and stored procedures to the new Database. Is there a way to do this? This report is going to multiple clients that each have their own naming convention so I would need to be able to change it dynamically. Thank you in advance for your help.
You can comfortably change the connection string and everything should work. This also depends on how you are accessing your data. If you are using standard datasets or some other ORM tool then this should work so long as you have exposed the connection string in your config file.
im using CR version 13. With VS2010 and CR SP1 for VS2010.
I have a report with lots of subreports. They use XML schemas for data at design time and then uses runtime populated datasets. It works great on my development machine. But on other development machines or in deployment the report pops up a databaselogon promt asking for username etc.
Ive seen alot of people having similar problems, nobody have an answear. Let me make it clear, i dont use a database in any way shape or form.
Other reports works ok, only my new report do this.
I had some subreports i wanted to supress. I did this by simply not setting any datasource on them. For some reason CR on my development machine didnt pop up a dialog for datasource, so i assumed it worked.
What i do instead now, wich is proberbly also the better way. is to give the report a parameter value wich is used in the supress formulas of the sub reports.
I am trying to produce SSRS reports to integrate with a MOSS Dashboard. Reporting Services 2005 only seems to be able to render .xls out of the box. Does SSRS 2008 have the ability to render in xlsx format?
To the best of my experience, exporting to excel2007 is not built into SSRS2008, you need to get an external component for that. Currently looking into what is available on the market, i'll get back to you with what i find.
Edit:
Ok had a look at both aspose.cells and OfficeWriter by SoftArtisans. Both claim to offer .xlsx-exporting capabilities for SSRS, but in both cases this is a partial truth at best.
Both work by having you recreate your report in Excel using their respective add-ons, and then pasting their own markup into your RDL-file. This also has the effect that if you are making an excel-exportable report in either tool, you won't be able to view or export it in anything else from SSRS. Both have the ability to open an existing report and access their datasets from there, which is a major advantage over trying to get MSQuery to work for you.
Aspose suffers from various issues with permissions on the server, where you need to grant it full trust (not everyone would want that). I also had a major hassle getting it installed properly.
OfficeWriter has some issues with shared datasources, where you generally have to go in and set them manually after you've published your report. It also seems to choke on VS2008 RDLs, if you want to use a dataset from a VS2008 report, you have to make a new report in VS2005 with your dataset, and use that as a basis for your excel-built report.
Personally I don't care much for either. But overall Officewriter does seem like it comes out ahead. Next stop is figuring out if it has built-in support for matrices, or that is something we would have to program in VB to get.
According to Exporting to Microsoft Excel(msdn)
The Excel rendering extension renders a report that is compatible with Microsoft Excel 97 and later.
This seems to suggest the old format.