Apex Code Development You need to sign in to do that
Don't have an account?
Do complex products (e.g. insurance, mortgages, etc) belong on the Products object?
Imagine a scenario where with each Opportunity there's the possibility for sales of multiple related financial products (e.g. mortgage, insurance) in addition to the main product (e.g. home sale).
An Opportunity is a potential property sale. So for each Opportunity record there's the possibility of one home sale, one insurance sale, one mortgage sale.
Selling these ancillary products is new so we currently we track the potential revenue related to the home sale directly on the Opportunity Object.
We agree that all these ancillary products cannot be put directly on Opportunity object but we've yet to develop consensus regarding where they belong: the standard Products object or custom objects.
Those in favor of the Product object say that approach is best because it makes aggregating all the revenue from the related product opportunities easily roll up to the Opportunity object.
Those in favor of the Custom objects wonder if the Products object can handle the complex needs of the business operations. The examples in Trailhead use Generators for the sample products. Another official Salesforce example (https://www.youtube.com/watch?v=6_htO6Ju0gU) of Product object in use shows furniture being sold.
But insurance and mortgages are very different than physical products. There are no Price Books for insurance or mortgages. Each client gets a custom quote from a third party. And the quantity for each product is always one. So it doesn't seem to be the textbook use case for Products and, if we did use it, it wouldn't look like the Salesforce examples.
Also, getting isurance or mortgage quotes are complex processes that involve humans performing various tasks at various stages of the insurane and mortgage product sales processes. But Path isn't available on Product which makes our users nervous beause they're familiar with Path and have asked for it.
Has anyone run into this question before? Any ideas on how to begin architecting a solution?
An Opportunity is a potential property sale. So for each Opportunity record there's the possibility of one home sale, one insurance sale, one mortgage sale.
Selling these ancillary products is new so we currently we track the potential revenue related to the home sale directly on the Opportunity Object.
We agree that all these ancillary products cannot be put directly on Opportunity object but we've yet to develop consensus regarding where they belong: the standard Products object or custom objects.
Those in favor of the Product object say that approach is best because it makes aggregating all the revenue from the related product opportunities easily roll up to the Opportunity object.
Those in favor of the Custom objects wonder if the Products object can handle the complex needs of the business operations. The examples in Trailhead use Generators for the sample products. Another official Salesforce example (https://www.youtube.com/watch?v=6_htO6Ju0gU) of Product object in use shows furniture being sold.
But insurance and mortgages are very different than physical products. There are no Price Books for insurance or mortgages. Each client gets a custom quote from a third party. And the quantity for each product is always one. So it doesn't seem to be the textbook use case for Products and, if we did use it, it wouldn't look like the Salesforce examples.
Also, getting isurance or mortgage quotes are complex processes that involve humans performing various tasks at various stages of the insurane and mortgage product sales processes. But Path isn't available on Product which makes our users nervous beause they're familiar with Path and have asked for it.
Has anyone run into this question before? Any ideas on how to begin architecting a solution?