Monthly summary template creation problem

AppSheet AppSheet Q&A
,
1

real data form will be summarized per month is to include the whole month’s data
If you want to create a template per month and have the date of that month to do?

numfon_naka_0-1662600465986.png
numfon_naka_0-1662600465986.png1722×470 28.6 KB

2

Since the question is very broad and we are not certain what data is being shown in the image, I’ll provide a very generic response.

There are 2 main ways in AppSheet (and most development platforms) to produce Periodic reports (Weekly, Monthly, Quarterly, etc.)

  1. Create a complex template to gather, summarize and format the app data as closely to your desired outcome as possible. How complex will depend on your data structure. In many cases you will want to provide some interim processing to help performance and reduce complexity of generating the report. Once a template is created then setup an automated process to run/execute the template and generate the report.

  2. Create tables that summarize the data as it is collected into a format as close to your final report as possible. The template creation and report generation process will be very simple and very quick. Advantage to this approach is that you can create views on the “summary” table for users to review at any time.

2a) Run an automated periodic process to generate the necessary rows in the summary tables all at once rather than as data is inserted.

What’s the difference?

Option 1) places a lot of implementation work into the template generation itself. Working in templates can be quite cumbersome - especially if the data is stored in a complex manor or requires complex calculations.

Option 2) and 2a) obviously pushes development efforts into table creation and processes to keep them updated or to populate them. You may need to add many tables to take steps in calculating the final desired results. I feel this approach does make it easier to identify and resolve any calculation issues

Which way you choose to go will depend a lot on your needs, current data structure and complexity. In most cases I think it is best to use option 2) as it disperses complexity AND provides flexibility in how you present information to users - i.e. views in the app, snapshot views , report generation etc.

2 Likes