We are moving to HEDA over the summer and I have a question concerning Salesforce native object [if enabled] AccountContactRelation (aka Contacts to Multiple Accounts - Released Summer '16).
- How, if any, does it impact HEDA?
- Can it be leveraged or other?
I would appreciate any insight you have; as I have not been able to find mention of it in 'Power of Us' group @Education Data Architecture .
Video Ref: http://salesforce.vidyard.com/watch/fxqHZf2pER29kXRYvkwio3
Summer '16: https://releasenotes.docs.salesforce.com/en-us/summer16/release-notes/rn_api_objects_new.htm
Hi @Buyan thyagarajand and @Dave Perry ,
The reason I am asking is for one, I think it needs to be asked... as It might thread-up later ;)
Some of the 'stated' benefits of "Contacts to Multiple Accounts" is the native click-not-code DML functionality when deleting account or re-associating the contact plus various roll-ups fields (ref.1) Not huge though similar'ish to HEDA. I would assume there was a discussion around the AccountContactRelation object when it finally came out (10 years and 64,650 points in the making (ref.2))
SFDC might count the junction object (AccountContactRelation) as a custom object with a 2K load per row. If SFDC did (though I don't believe they would),... I would sure miss losing an object worth of data if SFDC deem it as such.
For those migrating to HEDA & thinking about communities; managed packages do not count toward the 10 custom object limit (ref.3)
Anyways, it is always nice to know the determinations made during development.
Best - Paco
Ref.1:
http://salesforce.vidyard.com/watch/fxqHZf2pER29kXRYvkwio3Ref.2:
https://success.salesforce.com/ideaView?id=08730000000BrBSAA0Ref.2:
https://help.salesforce.com/articleView?id=users_license_types_communities.htm&type=0&language=en_US
