4 Answers, 1 is accepted
Reports are processed and rendered on the server machine. In general, there is mechanism for intersecting the rendered document before returning it to the client .- Modify exported report document prior serving it to the viewer client
Please note that Input elements are not used by the HTML rendering of reports. Input tags imply the ability to add content to a report, but this will be able only at the client and changes will not be saved in the report that is processed and rendered on the server.
If you need to add content in the displayed report, you can:
- Create custom UI that saves data changes on the server and then requests the report with the updated data;
- Use report parameters to add user input in the displayed report.
- Use Kendo UI to create UI allowing users to fill and export forms e.g. Grid/Export to PDF or Kendo UI Editor.
We will appreciate it if you elaborate on the scenario and the usage of Input elements in the report.
Thanks the first link is the answer for me. I'm not concerned with updates feeding back, I'll handle that outside of Telerik. Can you clarify what encoding is used for the Bytes property on GetDocumentEventArgs? I've assumed UTF8 as that appears in the HTML:
Is that right?
Also the menu option says "HTML Rendering extension." Is it possible to change that?
The scenario, is that we want to use Telerirk Reporting to provide a nice looking form which we will export/save and email out as an attachment to an external party. They will save the attachment, fill in the form, save and email it back. We will then process that outside of Telerik Reporting to get the updates back in the database.
i apologize for misleading you. The approach from Modify exported report document prior serving it to the viewer client is applicable if you export a report displayed by a viewer, which in the case of HTML will not work.
If you want only to get a report rendered in HTML, you can export programmatically the report and get the produced HTML pages:
The HTML pages will not work with the HTML5 Viewer, but you will be able to load them on the page as HTML content. The same can be achieved via custom UI or better by using a Kendo UI Editor that includes export options from browser. Kendo UI includes libraries which will allow you to export in PDF the HTML rendered in browser - Kendo UI PDF Export/ Document Export.
Having the above into account, my recommendation is:
- Use custom UI that allows the user to interact with it, to fill, edit, delete data and save it.
- Use Kendo UI to export the HTML in browser in PDF file, where you can use the PDF file as an attachment to an e-mail. Using HTML in e-mails is not recommended due to the different requirements of Email clients.
Or use Telerik Reporting to produce a report that contains the data saved by the user through the UI of step1. Reports should not be used for gathering the data.
Thanks for the extra info, but your first answer is working for me. The user who receives the html has no access to the system so they just save the email attachment (the html). Open it in whatever browser, fill in a value and submit the form which posts back to the system.