Users often ask for technical support when meeting difficult problems in designing reports. However, as technical support can’t link to users’ databases, they can’t preview users’ reports and find exactly the causes of the problems. Then technical support can only guess and give users advices like “Try method A”, “Or try method B” and so on. It’s not just a waste of time. What’s more, after trying again and again, users may still can’t solve their problems at last.
Is there any way to enable technical support to browse and debug a report without linking to user's database?
For users’ convenience, RAQ Report makes great effort to solve this problem. As a result, RAQ report invented a method-Built-in Dataset. It means to store the data of a report into the report template. Then, there is no need to link to user's database when previewing the report.
With the help of built-in dataset, technical support can solve users’ problems in shortest time.
Only built-in dataset may create another problem. When the dataset of a report is converted to built-in, users need to save the report as a new one, or else the original report would be covered and the dataset has to be edited again. Moreover, after the modified report is sent back by technical support, users have to modify the original report according to it again.
Don’t worry. In order to reduce users’ workload, RAQ report provides the function of Recovering Built-in Dataset. That is to say, users can recover datasets of SQL or other types when they are converted to built-in dataset.
Built-in dataset makes no obstacle between technical support and users. That’s great!
In the configuration dialog box of dataset, users just need to click a button to convert a dataset to a built-in dataset or recover a built-in dataset.