Hey team, would love to get your input on whether Knack can handle this type of app structure, or whether there’s a better way to structure this app so it requires less objects.
The app is a client portal where we would share patient data collected via a third-party tool (and would import via Zapier) on behalf of our clients. Our clients run research studies. Normally we would have a Study Object and a Patient Object. The challenge is that each study collects both standard information which is always the same plus other information that is unique to each study. There are approximately 300 studies, with perhaps 20 unique fields per study, which is a total of 6,000 fields (and we would expect this number to grow).
So having 6,000+ fields in the patient object doesn’t seem realistic. But I’m not sure if Knack can handle having 300+ Study Objects, a new object for each study. I’ve contacted Knack support about this but they’re not getting back to me.
I wonder if anyone has created an app with a similar number of objects? If so, did it work?
Or I’m also wondering if there’s a more streamlined way to structure the app that would keep the number of required Objects and Fields manageable?