Ask Search:
Benjamin SinclairBenjamin Sinclair 

Relationship Map Component Failing in Winter 20

We are an Enterprise Org, running with Financial Services Cloud.

Our Sandbox is encountering an issue with our Relationship Map - Financial Services Cloud Lightning Components.  Each place we are using this component, all we are seeing is the text "Looks like there's a problem", in place of the component.  

I've checked out the release notes for this component, and we're seeing the new controls for it in Lightning App Builder, but the component displays in the builder with the same "Looks like there's a problem" message. 

We have two sandboxes, and both are having the same issue.  Is anyone else encountering this issue?
Best Answer chosen by Benjamin Sinclair
chris camenzulichris camenzuli
I had the same problem but it was in Winter 20 there is a new field (FinServ__AssociationType__c) added to Account-Account Relationship object that no one (even system admin) has FLS. 

All Answers

Kevin EveryKevin Every
Im having the same issue as well. Please Update if you find an answer. Thanks
Benjamin SinclairBenjamin Sinclair
Please note, Salesforce Announced that some Orgs running FSC failed to receive the upgrade properly on September 6th, but if your org is showing a Financial Services Cloud version of 222.1, you were not impacted by this.  Our Sandbox orgs are showing version 222.1, and have this issue.
Kevin EveryKevin Every
Opened a salesforce case and their temporary solution was to add the Advisor access permission set to your users. 
Benjamin SinclairBenjamin Sinclair
Interesting.  None of our users had this permission in any of our orgs, but it does appear to correct the issue. I'll be interested in seeing if this is a permanent requirement moving forward.  Thanks for the follow-up!
chris camenzulichris camenzuli
I had the same problem but it was in Winter 20 there is a new field (FinServ__AssociationType__c) added to Account-Account Relationship object that no one (even system admin) has FLS. 
This was selected as the best answer
Benjamin SinclairBenjamin Sinclair
Chris,

We are on Winter 20 in our Sandboxes, as well. I gave access to that field to all users and the component is operational again!  

I didn't like the idea of giving everyone permission to an entire permission set just for one component, so this solution is preferable to our org!

Thank you!
John CrapuchettesJohn Crapuchettes
@Benjamin Sinclair

Do you have a link to something from SFDC saying this?
Benjamin SinclairBenjamin Sinclair
@John Crapuchettes

I don't have a link, no, but my ticket with SF Support has been escalated to tier 3, who is investigating my org now.  I will try to post after I get official word from them on resolution.
Ede HolmesEde Holmes
We have the same issue with the relationship map and in the sandbox we assigned the permission set recommended by SFDC support. It includes access to Account record types that the users are not allowed to create accounts in so it's not a workaround we can use.
Support just recommended that we give access to the field instead; FinServ__AssociationType__c.
Hopefully this will resolve the problem created by the latest release.
Ede HolmesEde Holmes
It seems to fix the issue! We will continue to monitor but after giving access to the field, users can use the Business relationhip map again.
Object:  Account-Account Relationship
Field Label:  Association Type
Erick CarlsonErick Carlson
I'm also seeing an issue with the relationship map.  Relations made from any Account Record Type to Individual Record Type - the relationship is made on both sides but from the Individual perspective, the relationship map is not updated.
Benjamin SinclairBenjamin Sinclair
Salesforce official answer to this issue is/was posted here, speaking to the correction for the Association Type Field:
https://developer.salesforce.com/docs/atlas.en-us.222.0.financial_services_cloud_upgrade_guide.meta/financial_services_cloud_upgrade_guide/fsc_create_expanded_aar.htm