case 4212
This commit is contained in:
@@ -184,6 +184,22 @@ Data here is displayed in the report designer user interface when the report des
|
||||
|
||||
If you do not see this section it means the report designer was opened directly without passing through a business object first so there is no current data to display but you can still edit the report as normal. This can happen if you open a report from a History form or use the browser back button to go back to a report that was previously edited or open a report URL directly.
|
||||
|
||||
## Menu options
|
||||
|
||||

|
||||
|
||||
In addition to the [common edit form menu options](ay-start-edit-forms.md#common-edit-form-menu-options) the Report edit form also has the following unique option:
|
||||
|
||||
### Export
|
||||
|
||||
The export option enables you to export a report template to an external file. This is used to share report templates, preserve them when erasing a database or simply to make backup copies when editing in case you need to restore a previous version.
|
||||
|
||||
Exported report templates are saved as a .json format text file with a \*.ayrt file name extension.
|
||||
|
||||
#### Importing report templates
|
||||
|
||||
Importing of report templates is done from the administration report templates [import option](adm-report-templates.md#import).
|
||||
|
||||
## Report data structure
|
||||
|
||||
When a report template is processed, business object data is provided to the template along with other data. Some of this data is used internally by the provided helpers and you have full access to these data values in your templates, Handlebar helpers and PrepareData scripts.
|
||||
|
||||
Reference in New Issue
Block a user