The order object has products much like an Opportunity has Opportunity Products.
We've modified our Opportunity to include some of the common fields you might find on an "order" object such as PO Number, PO Date etc...
I'm wondering what value, if any, I'd get from transistioning this data to the standard order object? Aside from collecting some additional data points in standard rather than custom fields, are there other use cases?
If you have a custom "order" object, how are you using it? If you plan on using the new standard Order object, how do you plan on using it?
31 个回答

I've always believed that from a business vocabulary perspective an opportunity is just that an opportunity to sell something and be done with it upon close. It should not be a long lived entity in that sense. It should eventually evolve into a Product or a service entity that the opportunity sold. So some other entity should become the bridge between an opportunity and a product/service that can be the contanier for onboarding/ provisionining processes without mucking around with a closed entity. I've found myself building order management processes in the CRM implementations I've done so far like what Cheryl mentions above. Typically the order takes the form of some variation of the opportunity. So imo, the Order object should be the standard for all activities after opportunity closed until product is live. I have felt the need for such an object very often in my industry (online advertising). Also then you can reference it with product and keep it for reference forever to answer questions like past orders from this customer and so on. Just a design and data model perspective. Otherwise we can always extend any object in salesforce in any way we want, it will work mostly!