Customers would like to be to install MAISED in house.

Add view data into imports grid and form. / similar to activities grid.

MAISED offers a generic charting facilities,
yet in many cases users want fixed charts , to load them quick and combine charts into reports, easy share sharts etc.

• dev basic charting facility using fusion charts
• dev basic set principle to chart multiple series
• prepare a follow up story for more advanced applications

Enable end users to easy create multi line charts/tables, share them via easy invite links, keep data up to date

Our users would like to have a parallel environment for testing/developing changes in the configuration prio to production deployment.

Add MAISED supports for more database environments

• add a sync functionality to sync data between the environments
• add interface to allow switching between DEV, ACC and Production environments.

A frequent request. Business makes planning per month. We want to split it per day with weights according to some other serie.

A import form accepts
Filter - weights data per day , year=2022 and activity_id = 99 and forecast_id =1

P1 array of monthly totals

App = month2day

The stored procedure

A view based on fact day joined with time date dimension.

Cte
Calculate totals per year month
Calculate day of month weight / should adds up to 100 per month
Calc month index / January would be 0 if whole year.

Turn the totals array into a table with index starting from zero

Join cte with totals table n index and multiply total on the day of month weight.

Insert data

By wrong date format no messages.

add error handling and notification

At more form when timed out, login form does not show up

Issues with timeouts when reading 10k+ files,
it was phpspreadsheet library, that abused memory trying to load all in once.
we implementen chunked loading filtering.
this increased the limits to 50K+ records or 10Mb files.

Import of large files will lead to time outs, even we implemented chunk loading in PHPSpreadsheet library.

there are two factors to that:

1. Loading file into memory
2. Deleting records
3. Inserting records

For 1 we plan to experiment with SPOUT library , which claims to be more efficient / memory optimal
https://github.com/box/spout

For 2 and 3 there will be separate use stories. Customers on premise can upload large files and then we can load whole file directly into the customer database schema