I have originally planned to lay out some custom json structure and write a big python script. Having read about grist I am currently running a local docker instance for what I call a “multi-project calculation tool”. I have always new ideas for projects which have different asset investments with depreciation, fixed costs and per-event costs. With the help of grist I’d like to have a quick way of calulating these.
As I would like to have a simple yet flexible interface I’d like to have the chance to enter not every month yet have the chance to create a list of costs|revenues|working hours which - to me seemed the most logical approach in grist concepts.
So for revenues I’d basically have a table that has following columns, it is mostly a boilerplate for all other things to come, only assets has additional columns for depreciation
- Project - select from project list
- Title - custom text describing the revenue type
- Repeat - linked to helper table that has year|month|day|week-integers and perEvent-toggle, last is actually the most reason why I need an event helper table
- End_Date - to eg. represent different project phases with different offers
- Months - Linked MultiSelection with Month-Names<>Numbers, should used to enable seasonal offers without having to enter any single year
- Amount - the price
- VAT - for future cash-flow
Now I’d like to summarize the amounts with the help of the bold fields. I first thought I could do some python code to do a rather big calculation which I think might break down the developement of additional charts and timelined statistics. So I am thinking of another helper table that lists all regular events with the bold parameters.
So eg. a row with
should create 8 (when date_end=24/01/01 > 16) rows that I can use to calculate all the costs that have the perEvent-Toggle and the other tables accordingly.
I hope I described my idea well enough and am open to different approaches, just not really able to sort this out.
Last not least - even not having finished my first grist-project - I find this an amazing tool and have already recommended other people to look at it. I am well sure that this so powerful I might use this in a commercial context one day and it is amazing that this is an opensource thingy I can try out so easily. Thank you!