@Filipa_Didier
I’ve PMed you a link to my modified version of your base, as I wasn’t sure how public you had wanted it. Frankly, if you’ve not made it public, I recommend you don’t: It is truly one of the most impressive bases I have ever seen, and it undoubtedly represents substantial intellectual property. I honestly found it quite inspiring: No only have you done an amazing job of leveraging Airtable both to capture and to facilitate your work flow, you’ve also made excellent use of Airtable Blocks as a way to isolate and document core business functions. @Zoelle_Egner, @Katherine_Duh, @Shani_Taylor, @David_Peterson and anyone else at Airtable tasked with helping users make the most of the product, I strongly urge you to contact @Filipa_Didier and ask if she’ll allow her base to be shared within Airtable for reference and training.
—— or maybe you’d be better off asking if she’ll share Version 2.0 of the base, as the current version is a bit of a mess. (On Filipa’s behalf, the current incarnation is probably more correctly Version 0.8 or 0.9, as most of the ‘mess’ is merely unused or redundant fields spawned during development.)
Again, out of concern for protecting potentially proprietary data, I’ll comment mainly over PM. What I can say in open is that I was able to implement a mechanism that greatly reduces both the amount of data retained and the amount of work required to enter and manipulate it.
For example, while my variation still requires a separate table to drive the Chart Block displaying fatty acid percentages, I was able to replace your 352-field [Product Fatty Acid %] table with a [New Fatty Acid %] that not only contains only four fields but is also entirely auto-generated. :winking_face: Admittedly, I had to beef up a couple of other tables a bit, occasionally with the help of some rather ugly formulas; however, most of the time I made Airtable write its own ugly formulas, which I then copy-and-pasted into the appropriate formula configuration field.
Caveat: I focused primarily on solving your maximum-field issue (and at the same time, I hope, providing some UX improvements). As a result, I have no doubt that, were I to go through the base and delete those fields I consider no longer necessary, I would break other critical functionality. I think you should simply be able to modify your routines to access my equivalent fields — that is, I don’t think I managed entirely to eliminate any data points — but there’s always the possibility I did.
I’ll take the remainder of my comments to a private channel.
Once again, a very impressive base, and I thank you for the opportunity to work with it.
