Hi @Shaun_Hornsby, and welcome to the community!
After a while? I think that ship has sailed. :winking_face:
Oddly, this question is best addressed with another over here.
There are three reasons we capture data:
- Compliance - what happened; when did it happen?
- Process - where do we stand; what’s next?
- Analytics - let’s make a decision.
Data modelling is a delicate dance that must embrace each of these key objectives. If you have a data model that cannot effectively embrace the requirements of #3, you need to fix that in the model with deference to the limitations of the database platform, …OR… you must backfill the weaknesses with script automation.
In my view, you are missing a key aspect in your data model - separation of state data from transaction data.
State data is like company details; there is one (and only one) record for each company. It is immutable and while it changes from time-to-time, it is very different from transactional data.
Transaction data is like sales; it’s a log or ledger of activity.
It appears your data model is conflating these fundamentally different information types. To not do stupid, you need to separate them and utilize links to formulate a relational database model.