When creating events with attendees, a child event record is created and assigned to each attendee who is a user.
Each child event copies the field details from the parent event. However, it's an expected behavior that there is no direct reference that an event is a child record and there is no actual lookup field referencing the parent event.
To check if a record is a parent or a child, use one of these standard references:
Note: A child event record isn't created for contacts or leads.
For this functionality, perform the steps listed below and create the Flow:
1. Go to Setup > Object Manager
2. Select the Activity object
3. Click on Fields & Relationships
4. Click New
5. Choose URL as the data type, then select Next
6. Set the Field Label as "Parent" (the Field Name should auto-populate to "Parent")
7. Click Next
8. Set the Field Level Security as needed, then click Next
9. Add the field to the Event page layout, then select Save
1. Go to Setup > Flow
2. Click New Flow
3. Choose Record-Triggered Flow and click Create
4. Configure Start Element
5. In the Start element, configure the following:Object: Event
6. Trigger the Flow When: A record is created
7. Set Entry Conditions:Field: IsChild
8. Operator: Equals
Value: False
9. Optimize the Flow for: Actions and Related Records
10. Select Done
11. Select the + icon to add an element > Update triggering record
12. Enter the label Update Parent Field and select Done
13. Configure the following settings:How to Find Records to Update and Set Their Values: Use the event record that triggered the flow
Set Filter Conditions: None- Always Update Record
Set Field Values for the Records:Field: Parent__c
Value: Equals https://ap5.lightning.force.com/{!$Record.Id}
(Note: Replace "https://ap5.lightning.force.com/" with the home link to your Production organization.)
14. Click Done
15. Save and Activate Flow
16. Click Save
17. Enter the Flow Label as Populate Parent Field with Event URL (the Flow API Name will auto-populate)
18. Click Save
19 Select Activate
000383259

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.