Hi there,
I’m facing an architectural problem for which I haven’t a solution as of yet. This problem is linked to the way I handle revenue and payment depending on the client type – small company or big company.
Here’s how I decided to structure my database to handle revenue and payment for small companies:
And here’s how I decided to structure it to handle the workflow for big companies:
But this leads me to the following problem in terms of database design.
I could have found a solution to this problem by:
- breaking the [Revenue Items] – [Client Sessions] direct relationship
- pulling the Client Sessions into the [Revenue Items] table with lookup fields and assigning each of them to the proper revenue item in dynamically filtering them based on their execution date
Only problem… dynamic filter is not offered on lookups! That means that all client sessions for the deal are assigned to each revenue item, instead of having only client sessions of January be put into the bucket of the February revenue item.
Since artificial intelligence couldn’t offer a satisfactory solution to that problem, I’m now resorting to natural intelligence! Any smart database architect out there who’s got a suggestion?
Thanks.