RingCentral for Salesforce: "activity" fields to be reduced from 16
RingCentral for Salesforce: "activity" fields to be reduced from 16. @Matt LaHatt wrote:Our SalesForce integration has been a hot topic of interest for them. They loved the demos of it and love the features a value we provide. However, they have a major dilemma. Bessemer has 2x custom integrations that use up the majority of the 100 custom fields. They only have 12 fields they can make available for the RingCentral integration. I've heard from others in our organization that our SFDC integration requires 16 fields to work.@Matthew Ludwig wrote: SFDC has max 100 fields available under the "activity" object. RC utilizes 16. I've had circa 20 customers/prospects complain of this over the past year. from a dev perspective: RC has placed all 16 fields under the "activity" object, and we have "obsoleted" fields too.zm has an advantage as zm spans multiple objects zm (classic): 10 (activity) zm for Lightning: 5 (activity) @Sam Rizzo wrote:> @Dan Buck - Looks like Zoom got around this by not attaching everything to the activity parent object> They'll attach something like "Zoom Call Log" to activity, and then things like the start/end time of calls/etc link to "Zoom Call Log" instead of directly to "Activity"> RingCentral instead links everything to the Activity parent object @Dan Buck wrote:> Just to be transparent, to remove Activity custom fields and objects, even obsolete ones, is a very complex request. Based on my discussions with RingCentral Dev resources, even if we could reduce the count of Activity fields to ~10 it would be extremely time consuming and would require assistance from Salesforce dev resources to make sure we don't lose any customer data when making this sort of change.