I’ve built a proposal / quotation app. Some items are made up of components. For example: Stitchliner - 1 x AFC-50, 1 x SPF-50 and 1 x HTS-50. What I would like to do is to select the Model Stitchliner and automatically add the related components. Another example would be an accessory which is made up of 3 components : 1 x item 1 and 2 x item 2.
Adding singular items is straight forward but I’m stuck on selecting the Main model and auto adding it’s components.
I’ve done this in excel which is pretty straight forward as it’s a simple cell formula but I’m stuck in Glide. Has anybody done this before? If so, could you provide some guidance?
cheers
I assume the question is in the context of a form, where a new row is being created?
Given that, how should the sub-components be added? ie. should they be added each on a separate/new row, or together as a single value with the parent item?
Okay, this is not a simple thing to do in Glide. To add related rows automatically when a parent row is created requires all sorts of gymnastics using a helper table and the Glide API. And it’s not something I can explain in a few sentences.
Given that the end result is a sales proposal, I wonder if it might be better/easier to generate the line items at the same time the proposal is generated?
How is that done - are you using one of the PDF integrations?
Click New proposal and fill out a form: Proposal number, Company name and details.
Create proposal
Add products.
Create PDF: At this stage it’s DocsAutomator.
Once the proposal is complete and accepted I’ll submit to turn it into a contract and generate a contract PDF to sign.
The reason for automatically adding components is some machines have a number of compulsory components which need to be ordered separately. The purpose was to have it listed on the documents so nobody had to think about what was needed. Anybody creating a contract could do so without thinking. It’s what I’ve done on the excel spreadsheet for different machines.
Not sure what you mean? I currently have the parent and then an array column for the components.This then allows me to relate them back to the parent and show a list: