My understanding: If you’re developing your own app/module, a standard report will be saved in the module definition, and will therefore be deployed wherever the app is installed. A custom (non-standard) report is specific to the site and the definition is local to the database.
2 Likes
The choice is yours as to where you want the definitions (metadata) of the report to be save to : either on the File System (Is Standard : Yes) or to the database (Is Standard : No).
If the report is defined as Is Standard : No, then no File System files are generated and all of the report definitions are persisted to the Database and not to files on the FS. I explain this in the first few paragraphs of this tutorial [Tutorial] Script Report / Chart. This does not always hold true for all definition properties, eg add_total_row etc.
The choice of the term “Is Standard” is such a shame as the ‘Custom?’ for DocTypes, Workspaces, etc and the ‘Is Standard?’ for Script Reports, Notifications, etc work similarly. Both being indicative of it being built-in (standard !) on the FS of the app or a customisation (custom !) to the app stored in the DB.
With Scheduler Event and Notification, this distinction is not as clear cut, and on occasion both mechanisms are used irrespective of your choice. The problem arises when you alter the selection and save and then revert your selection. This causes a remnant of the former either in the DB or on the FS, with unexpected behaviour. Caveat emptor !!!
Hello @Divya_J
You create it precisely the same way: Awesome Bar > New Report.
Then give it a Report Name : [YourReportName] and select Report Type : Script Report.
Then when you specify Is Standard : No, then a field named Query / Script is rendered which does not render for Is Standard : Yes. Is Standard : No is actually a customisation to the installed App to which you assign the report to with the Module : [YourCustomApp]. This script is saved in the DB of the Site on which you’re working on, it is not part of the built-in features of the App, ie saved to the file system of the App.
If you want to deploy this report / chart to a production server, then you have to export this customisation as a fixture. Fixtures are packaged with the App and installed when the App is installed.
See this topic for instructions on how to define a Report / Chart completely on the client-side, without the need to deploy it from a development server to a production server. [DevTip] Custom Reports, purely client side