Add Relationship Map to a record page
This article is for Salesforce admins at Relationship Map-only customers. When you finish, you have created the lookup field in your org, the map component is on the Lightning pages your team uses, and a test user can open a map from a record without Crush.
Crush customers: stop here. Your map sits in PROLIFIQ RELATIONSHIP MAPS (plural) on Account Plan. Do not add the singular component from this article.
The package does not include a lookup from Relationship Map to Account, Opportunity, Campaign, or any other host object. You create that field. Until it exists, the component cannot render a map on that object.
Before you start
- Relationship Map is installed. Install Crush Suite or Relationship Map.
- You can edit custom fields and Lightning record pages (typically a system administrator).
- Pilot users have a Relationship Map permission set. Assign Crush and Relationship Map permission sets.
You do not need Crush, an Account Plan, or Cross-Sell.
1. Create the lookup — you provide this field
The component finds a map by walking a lookup relationship between Relationship Map and the record you are on. That field is yours to create. It is not part of the managed package (Salesforce does not let customers edit packaged metadata, so the host lookup has to live in your org).
Create a Lookup from Relationship Map to the object you will put the map on. Account is the usual first object.
- Click the gear, then Setup.
- In Quick Find, enter Object Manager and open it.
- Open Relationship Map.
- Open Fields & Relationships, then New.
- Choose Lookup Relationship, then Next.
- For Related To, choose Account (or Opportunity, Campaign, or another object). Next.
- Enter a field label your admins will recognize (for example Account). Finish the wizard: add the field to the Relationship Map page layout, and grant Visible field-level security to your Relationship Map permission sets.
A lookup on the host object that points at Relationship Map also works. One relationship in either direction is enough. The usual pattern is the lookup on Relationship Map, pointing at Account.
Repeat this for every object you will host a map on. Account does not cover Opportunity. Opportunity does not cover Campaign.
Campaign is a standard Salesforce object. Creating Campaign records requires the Salesforce Marketing User checkbox on the user. That is not a Prolifiq permission. People who only open a map already on a Campaign do not need Marketing User for that.
2. Add the component
In Lightning App Builder the package exposes two similarly named components. Relationship Map-only customers use the singular name.
| Who you are | Component in App Builder |
|---|---|
| Relationship Map only | PROLIFIQ RELATIONSHIP MAP |
| Crush | PROLIFIQ RELATIONSHIP MAPS — not this article |
- Open an Account (or the object you related in step 1).
- Click the gear, then Edit Page.
- Find PROLIFIQ RELATIONSHIP MAP and drag it onto the page.
- Save, then Activation if Salesforce asks you to activate the page.
If you only see the plural name, you are on a Crush org. Do not follow the rest of this article.
If the map does not load
Without a lookup, the component shows:
Cannot fetch or auto-generate Relationship Map:
There are no relationship fields for the map
That means this object still has no lookup relationship with Relationship Map. Create the field in step 1, then refresh. Do not keep adding the component hoping it will invent the relationship.
If the field exists but the user cannot see it, you will get a field-level security error instead. Grant FLS on the lookup you created to the Relationship Map permission sets.
How the page finds a map
When someone opens the record, and the lookup exists:
- A lookup on the host record that points at a Relationship Map, if one is filled in.
- Otherwise, a lookup on Relationship Map that points at this record. If more than one map points here, the component uses the oldest map.
- If none exists and auto-create is on, the package creates a map (when the user can create one) and fills in the lookup.
Relationship Map Settings has Auto generate Relationship Maps. It defaults to on. Leave it on unless you want people to create maps only by hand.
Auto generate Relationship Maps on that page writes the org flag used for Opportunity, Campaign, and other non-Account hosts. Maps on Account follow a separate org flag, Auto Create Stakeholder Maps (also on by default). Changing Relationship Map Settings later does not rewrite chart settings on maps that already exist.
Canvas lock and card style
Once the map is on the page, editors can:
- Use canvas lock (the lock control on the map toolbar) when they want cards to stay put. Zoom, refresh, and fullscreen still work. Dragging people around the canvas does not. This is a per-map setting, not a permission set, and it is not PROLIFIQ RELATIONSHIP MAP Read Only User.
- Set Card Style to Detail, Compact, or Fixed Size in chart settings. Fixed Size is the packaged default.
Org-wide defaults live under Relationship Map Settings. Org settings and setup checklist. Users change one map when Show Chart Settings is on. Customize a Relationship Map.
What “done” looks like
- Object Manager shows a lookup you created from Relationship Map to Account (and to any other host you use).
- A Relationship Map-only test user opens that Account and sees PROLIFIQ RELATIONSHIP MAP, not the missing-relationship error.
- They can create a map and add people without an Account Plan.