Skip to main content
Question

Using QB for CPQ app?

  • Sep 21, 2023 3:41 PM UTC
  • 0 replies
  • 139 views

Forum|alt.badge.img+11

I've been using QB for ten years for our company's quoting system. We're at a point where we need to decide about upgrading to a CPQ (configure/price/quote) app, for accuracy and integration with our ERP. I searched this form and exactly one reference to CPQ. My experience with QB imagines all things are possible, but CPQ can be complex and I'm not sure if buiding something from scratch is the right answer.

Specifically on my mind, as a builder, I am not experienced in making rules that a configurator would require, where the conflict of daughter items is resolved (can't buy tinting if a window isn't included). I have a few times I've done something like that, but feels like a work-around, and would be core to CPQ. Especially when the user changes their mind about which items they want.

Anyway, just looking for some feedback, from the community about this, thanks.



------------------------------
David Jung
------------------------------
This topic has been closed for replies.

MarkShnierYou
Forum|alt.badge.img+24

Well let me weigh in with a random opinion. I have been working with Quickbase first as a kind of power user when I was a manager and then after we sold our family business as a developer, in all since 2002. so 20+ years.  I have worked with I imagine more than 100 clients and countless apps. And all I can say is when you get into the intricacies of building an app with crazy business rules, there's always a way to do it with QuickBase one way or the other.  

The famous Quickbase sales engineer Kirk Trachy, now retired had a great expression. "If you can say it, we can do it."   And what he meant by that is if you can clearly enunciate in words, the business rule or the formula or the restriction that you are trying to implement then we can do it. The challenge often becomes being crystal clear about what the requirement is.   

We have so many tools now at our disposal compared to the early days. Pipelines, formula queries, URL Formula buttons and regular old relationships.

So for example if I was to guess what you meant about your original question, if we are building an order and it has Child Line items the order can easily detect through very conventional summary fields whether or not there are any child items in category windows.  That would allow us to control whether or not we will let you add another child item as tinting.  Simply be a form rule which blocks the safe and put up a message to the user. "Cannnot I add tinting because no windows yet".    

 



------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------

Forum|alt.badge.img+3
  • Observing
  • Sep 21, 2023 5:50 PM UTC

David,

I've created several inventory and estimating forms for our business. Managing all the fields and actions can be a bit tricky, but once you get the hang of it, they work really well.The trick is always to build for scale.  I've learned how to do this on my own, mostly through trial and error.

If you're already using Quickbase, it's convenient to have everything in one place, in a familiar environment. However, I wouldn't recommend it for beginners unless your system is super simple and won't change much or often.

In my experience, formulas tend to be more dependable than form rules. Both have their uses, but I've found that formulas consistently give better results.

I hope this information is helpful!



------------------------------
David Hyde | Director of Technology, Systems Dev. and Data Analytics
BWW, Inc. dba SERVPRO® Team Wilson
Locations in Birmingham, AL | Dallas, TX | Houston, TX
------------------------------