Would like the RESTful engine to be able to return plain text instead of base64 encoded response for CSV output
Would like the RESTful engine to be able to return plain text instead of base64 encoded response for CSV output requests. Currently, all responses are returned base64 encoded which wouldn't be necessary for a CSV report just plain text would be better.3 votes
RESTful engine async does not check for the validity of the report request and immediately returns a Guid. It would be prefered that the RES
RESTful engine async does not check for the validity of the report request and immediately returns a Guid. It would be preferred that
the RESTful engine checks immediately and return an error message instead.1 vote
We are trying to use the RESTful Engine to print reports (autotag templates). Currently, there is no feature to send a request for multiple copies of a job. If you need to print 3 copies of the same report, you will need to send the job 3 times. It will be great if you can command to have number of copies to print.1 vote
Currently when passing and XML or JSON data source within a REST request it has to be encoded into base64. It would be very valuable to be able to pass the XML or JSON data directly within the REST request.1 vote
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
While processing through a dataset I use the following code:
if(report.GetStatus() == Report.Status.Error)
What needs to be added is a way to see and report back to the user what failed. Why is the report in an error state.6 votes
I wanted to follow up on this suggestion. We have made many improvements to the RESTful Engine in recent years, so I wanted to ask if this was still an issue for you. We are looking to improve our errors in the future to be more clear, so if this is still an issue we will consider adding it to that effort.
Thank you for your suggestion.
- Don't see your idea?