Hello there,
I am new to Grist and have been exploring its features for a few weeks. I must say; I am impressed with the flexibility it offers; especially for building custom workflows and database solutions. Although; I am now working on a somewhat complex project and would appreciate some guidance from the more experienced members of the community.
The project involves managing a large dataset that tracks different types of entities. Each entity has its own set of attributes and relationships; but there is also quite a bit of overlap between them. For example; a customer can also be a vendor; and both customers and vendors can have overlapping attributes like contact information and locations.
What is the best way to organize this in Grist? Should I create separate tables for each entity; or would it make sense to combine related entities into a single table and use tags or categories to differentiate them? 
How do I effectively manage relationships between entities? Is it better to use reference columns, or is there another approach that might work better for handling things like orders linked to both customers and vendors?
Also, I have gone through this post; https://community.getgrist.com/t/could-someone-give-me-advice-on-optimizing-database-performance-for-large-datasets-minitab/ which definitely helped me out a lot.
Are there any general best practices or things to avoid when designing a data schema in Grist for a project of this scale?
Thanks in advance for your help and assistance. 