Hoping to get some insight into how to build an airtable base.
Context: Our business development department is collecting information internally on prospective vendors. They’ll then input the information into airtable with the expectation that all documentation can be outputted into 1 seamless “packet” of information taking all documentation from airtable.
Here are the requirements of the base:
Here is a ROUGH draft of what I’m thinking (needs a lot of ironing out)
I have a very quick turnaround time and would like to have this ironed out this week. Please let me know if you can help. Ideally I would like to chat over the phone.Thanks!
Being an experienced Airtable consultant, I can say with great confidence that what you are wanting done is well within my area of expertise.
You can reach me on firstname.lastname@example.org
@Rachael_Castelaz, I’ve encountered something similar as well and you have some good consultants ready to help. Indulge me while I provide some advise from previous engagements - this might help you with your strategy.
It’s been my experience that there are few options to address this final requirement - arguably the most important requirement - without integration code of some type and without a framework that is document-centric and which is programmable.
Creating precision output in the context of the workflow process is difficult because Airtable lacks a few essential elements at a foundational level. This will change in the future, but for now you must press on without true event handlers and state transitions to come up with a solution.
Page Builder is not likely to make it the last mile of the requirements but I defer to some of the clever consultants who have responded. It’s certainly worth a try.
To overcome these Airtable limitations and achieve precise document/reporting standardization in a similar project, I used Google Documents to create, manage, and render standardized templates, and Google Apps Script to fabricate the necessary workflow automation. Here’s an example.
This is a rational fear because it suggests a very complex process. Ideally, you want to avoid this because there’s a good probability that you’ll encounter new document-bases conversations. In some way, your consultants need to create an abstraction layer to avoid more than one table that addresses arbitrary document formats.
Best of luck with your project - it looks like a good candidate for my next recommendation - clear requirements before settling on any specific implementation approach. :winking_face:
Hi @Rachael_Castelaz !
I sent you a PM.
You can schedule a time with me here: https://calendly.com/cherryyang/initial-consultation
Here’s my website if you’d know to know more about me. https://www.airopsconsulting.org/
Look forward to connecting with you and have a great rest of your day!