Page History

...

• write the query as a FUNCTION
• in addition to the SQL query, set up a JSON file to configure the report display and parameters
• use naming conventions, e.g., LTS_ACQ_1_name_of_query
• make sure the report does not include sensitive data, such as patron identifiers (e.g., user_id, requester_id)

Publishing the report

• test the report by running it as a FUNCTION in Metadb
• save working version of the query and its companion JSON file to reporting_app_dev
• to publish, post the query and its companion JSON file to the reporting_app directory
• run the report as a FUNCTION in Metadb
• verify that the saved function is in the Functions directory in the z_reporting user account schema
• test the report in the FOLIO Reporting App

...

• LTS_ACQ_1_sopo 
• LTS_ACQ_2_orders 
• FBO_1_daily_appr_inv_exported_yesterday 
• FBO_2_daily_appr_inv_vendor_yesterday 

Documentation Links:

• There are more specific instructions for creating Reporting App reports here:
  https://github.com/folio-org/ui-ldp/blob/master/doc/reports.md
• Stefan created a nice set of information on the folio-analytics wiki on UDFs, which includes information on writing functions for the Reporting App here:
  https://github.com/folio-org/folio-analytics/wiki/Cookbook:-User-Defined-Function
• We also have the FOLIO documentation info, which is helpful for Settings and Permissions, here:
  https://sunflower.docs.folio.org/docs/reporting/reporting-app/

...