I have posted a new post with some Use Case examples on how to leverage the Sugar Framework to add additional functionality. What are your thoughts? Do you have more use cases I can add to the list?
I have posted a new post with some Use Case examples on how to leverage the Sugar Framework to add additional functionality. What are your thoughts? Do you have more use cases I can add to the list?
hey Jeff Bickart
I think Sugar could do with some help for implementing CRM for customers that have a B2C customer base rather than just B2B, or even better to have ability to deal with both.
i.e. a business that has all B2C customers that place orders from a website, and also has to manage relationships with their suppliesr (B2B).
.
It is possible to configure as Sugar B2C; You can enable this property, require_accounts
Jeff Bickart
Doesn't cover Quotes module, which has specific need to associate an Account to every line item, so not as simple unfortunately.
Jeff Bickart
Doesn't cover Quotes module, which has specific need to associate an Account to every line item, so not as simple unfortunately.
I guess I never realized this, but we don't populate Account on Quoted Line Items....
This is pretty easy to do via a simple js customization.
I don't believe that the OOTB (out of the box) Sugar displays the Account on the Quoted Line Items. This must be a configuration for your instance
I does not show on my QLI in the Quote record view on mine (though my QLIs were customized a long time ago), it does show in the Products record view though, and it looks like mine are all blank. Although I don't think we changed anything to make it so.
The related Account is only viewable when you click on the QLI to view the record detail.
I believe it causes issues if each QLI doesn't have a related account.
.
CRM Business Consultant
By default the account_id on QLI is set on saving it (BaseProductBundlesQuoteDataGroupListView.onSaveRowEdit).
Double check if it is not being overridden somehow.