Disconnect DataSets from Datasources. If we could create a dataset seperately (Like we do with Query Tags) we could have datasets defined in the template itself and not in the datasources. This allows us to change the datasource when generating the template on the Staging or Prod machines and still have the same subset of data selected.
It would make templates much more reusable as we could define a handful of more general datasources and limit the data requested by using DataSets in the templates.3 votes
Could you please provide some additional information on the problem being solved: does the data you are using in staging and production have different structures? What data provider are you using? At runtime you can specify the connection string for the Datasource and the query to be used for the Data Set, are these two capabilities insufficient currently to resolve your problem? (Please note that Datasets were changed sometime around version 16.1. These new Datasets are what I am referring to vs the pre 16 Datasets.)
We current switched from the .NET engine to the RESTful engine and discovered that we lost the ability to create Text reports. For some reason the RESTful engine does not support this simple file output. Can you please put this feature into the RESTful engine? We have many customers that require text reports that are directly loaded into mainframes and/or other hardware and we can't provide any other file format.1 vote
We have accepted this idea for future development. I will update this ticket again when the idea is targeted for a future release. Thank you for your suggestion, and please submit any other ideas you have to improve our products.
- Don't see your idea?