Max fields per table?
I am working on a project management tool that stores projects, notes, sales data, and survey data. The survey data can be a lot of fields when we survey. To me I would think it should be isolated ...
Forum Discussion
I do not recommend hard coding 30 to 50 fields on the project record for the survey questions. You should have a model project(s) with a child table of Standard Survey Questions.
Then use the Copy Master Detail wizard function in App management to create a button which will copy those questions into your Project.
I don't have time right now to go into a lot of detail, but I will come back to this question when I have time.
Here is some help on that.
https://help.quickbase.com/user-assistance/copy_master_detail.html
feel free to post back if you have questions.
Then use the Copy Master Detail wizard function in App management to create a button which will copy those questions into your Project.
I don't have time right now to go into a lot of detail, but I will come back to this question when I have time.
Here is some help on that.
https://help.quickbase.com/user-assistance/copy_master_detail.html
feel free to post back if you have questions.
So not sure if my request was clear as this isnt making 100% sense to me....
All of the survey data is the same for every project. It is the same list of questions each time. The answers are sometimes not always available at the start of the project so we continue to feed the survey with new information as we learn it.
That is why I was thinking they are all table fields. I am not quite following who or why I would use a copy records button?
All of the survey data is the same for every project. It is the same list of questions each time. The answers are sometimes not always available at the start of the project so we continue to feed the survey with new information as we learn it.
That is why I was thinking they are all table fields. I am not quite following who or why I would use a copy records button?