Skip to main content
Question

Quote Tool Design Thoughts

  • October 17, 2025
  • 0 replies
  • 205 views

Forum|alt.badge.img+6

I have a need for a unique quote tool, and I am seeking some design methods with pros/cons. My initial design draft is something like this –

 

I have a Quote table form with some buttons to add a specific product. The issue is that adding each product, while easy enough, will place products in their own report link on the Quote Table form.

 

Yes, I could have all products and configuration items in one “Products” table so that my quote table line-items are in one report-link, but now my field count within the “Products” table will easily exceed 500+ fields and make it worse to manage.

I've attached my design thoughts (image)

Thanks so much for any feedback

Forum|alt.badge.img+11
  • Registered
  • October 17, 2025

Unless the products are wildly different from one another, I think the best approach is that you used 1 table for products. Even if you have some 500 fields, they can be organized with a naming scheme and would be displayed on forms conditionally not all 500 at once.

But if you couldn't do that for some reason, then another option (if you have separate tables for each product) is to use the API to run reports for each product. Then using Javascript, you can output what would visually look like 1 single report. The customer wouldn't be able to tell the products are from multiple tables. This solution would be in a code page which you can embed on the EOTI form.


Forum|alt.badge.img+15
  • Registered
  • October 17, 2025

What are you selling?

There is some sort of architecture about your line items on the quote that should fall out.

Products Table?

Service Table?

Maybe an Item Master with Vendors above that?

500 fields sounds like a lot.  Do you first need a Product Configurator to build a BOM which then goes on the proposal?   Perhaps a table of Sub Assemblies that then go to the Product and then the proposal.