welcome to the community! ![]()
your use case is very achievable in coda ![]()
because there is quite a number of fields, i would suggest utilizing the “Detail” view with non-native stylings as demonstrated by @Andrew_Farnsworth here.
Another option I was going to explore since the width (in terms of rows) of info is so wide, breaking the single use fields up into groups, with each group being its own table, limited to 1 row per project.
are these fields related? e.g. car model and make or are they related to the incident?
if the latter - i would advise not to go down this path.. it will get unwieldy fast. If anything, still put the groups of fields in same table (main one i.e .cases) and then create a view for each group and open up a modal to fill in the group.
hope this makes sense and hope this helps!
cheers!
Mel