Thanks for the advice on the previous question about best practices. I'm starting to reframe my thinking about structure in SmartSuite, but now I'm left wondering why have multiple solutions when I can have huge tables and organize everything just with groups, views, and filters?
As an organizer by nature, I hate the idea of having a big Master Solution that just has all of our CRM in one table, all our Event records in another, and all the Generic Tasks in a third, with a fourth for "Projects" that just reference these three without being "home" to much data themselves. But on the other hand, with good grouping and contexts, isn't that just better than multiple solutions? And with good enough view creation, would you ever be able to tell the difference, honestly?
I get that there are table limits and record limits, so that can cap things, but with linked records, it feels like "height" is just an illusion, and flat data is best data in most cases.
One other thing is that it feels easier to reference other things within a solution than it is to reference things outside the solution--but I may be wrong. My bosses want me to basically make all the cross-references into hyperlinks (essentially) that let you travel from one table to another and that seems easier when it's all within the same solution.
Am I starting to visualize this correctly? Is there ever a good reason to have a ton of solutions or create special solutions for projects, or do things like assign projects their own task lists rather than just reference a master task list via groups/contexts and filters?