We are looking for a way to access data from past configurations, so anytime a system is reordered, the original configuration can be referenced and – basically – duplicated without going through the entire configuration process.
Our original idea was to write any relevant data (part number, description, qty, etc.) to a table when a configuration is complete. In a future configuration, the desired part number would be entered, the table would be queried, and all the relevant data would be pulled into the configurator. However, there doesn’t seem to be a way to edit tables using snap rules, so this idea probably won’t work.
I’m wondering if anyone currently has a working method for storing/accessing data from past configurations. Ideally this would take place within CPQ during run time, but any suggestions are welcome!
It might be worthwhile to explore the records that CPQ is already keeping itself. For example, in the CPQ database the QuoteProduct table has an interesting looking column named ConfiguredProductJson; maybe that contains json-formatted details about the configuration in a quote. But they’ve stored it there as a varbinary type, so unpacking it might take some research.
Regarding editing tables: other 3rd-party products do have full editing access to custom tables in the CPQ database. So if you don’t find a way to do your edits directly from snap logic, you could set up something on the web outside of CPQ that does the editing. (And then maybe you could use “safe functions” to have snap logic send data to that thing.)
We were able to create snap logic that edits tables, so now we’re working on building out logic for the feature described in the second paragraph of my post above.