Modifications made to the SharinPix Plan component on child records can be reflected on the parent record.

This section demonstrates how to configure the plan component on the custom object Room (child object) and the Account (parent object) object so that modifications made to the child records' plan component (Room records) are reflected on the parent's plan (Account record). 

For this configuration you should:

1. Create SharinPix Plan Settings for the parent object using the Custom Metadata Settings. 

For detailed steps on how to create SharinPix Plan Settings for the Account object, click on this link.

2. Create SharinPix Plan Settings for the child object using the Custom Metadata Settings. 

For detailed steps on how to create SharinPix Plan Settings, click on this link.

3.  On the Account page layout (the parent's page layout), add a SharinPix Plan component and configure the same using the Lightning Page Builder. 

This step is documented in this article, but for quick reference, here are the mandatory parameters to be populated on the parent's SharinPix Plan component:

• Plan Data Field API Name: Name of the plan data field created on the parent object.
• Background Image Tag: Tag to be used to identify the plan image. The image can be uploaded and tagged on a SharinPix Album.
• Height: Height of the component.
• Mode: The parent plan component should be preferably on Geocode or ReadOnly mode. If you want to enable users to add markers on this component, the mode should be set to Edit.
• SharinPix Plan Setting: The object’s SharinPix Plan Setting name (as created in the Custom Metadata Setting).
• Marker Label Fiel API Name: The field API name stores the marker label. This field should be created on the SharinPix Plain Item object. For example, Name or sharinpix__Title__c

4. On the Opportunity page layout (the child's page layout), add a SharinPix Plan component and configure the same using the Lightning Page Builder. 

Here are the mandatory parameters to be populated in the child Plan component:

• Plan Data Field API Name: Name of the plan data field created on the child object.
• Background Image Album Field API Name: The parent lookup API name (as created on the child object). This will display the parent’s plan image on all child records.
• Background Image Tag: Tag to be used to identify the plan image. This value should be the same as the parent’s Background Image Tag (i.e., the same tag value should be used on both parent and child plan components).
• Height: Height of the component.
• Mode: The parent plan component should be in Edit mode.
• SharinPix Plan Setting: The object’s SharinPix Plan Setting name (as created in the Custom Metadata Setting).
• Marker Label Fiel API Name: The field API name stores the marker label. This field should be created on the SharinPix Plain Item object. For example, Name or sharinpix__Title__c

5. Once the Plan components have been set up on both parent and child page records, create an automation that will trigger (example: a Record-Triggered Flow) on every related SharinPix Plan Item record created at the child level.

Once the automation is triggered, it should update the parent lookup field on the newly-created SharinPix Plan Item record to the desired parent record. This final part will ensure that all markers added to child records are displayed on the parent record.