Prerequisites

1. This article only supports automation for organizations that define nested folder structures ad described in this article: How to mimic a Salesforce object structure in SharePoint
2. The parent object automatically creates a child object folder in its initial folder structure.  (For example, when an Account folder is created, an "Opportunities" folder is created to hold child opportunity folders.)
3. The Child object has a root folder override field that references a child folder of the parent object.  This field must be specified in the App builder "Root Id Field API Name" (For example, the Root_Folder_Override__c field on Opportunity has a formula field with a value like:
   • Account.Sharepoint_Folder_Id__c + ",Opportunities"

Procedure

Once your environment is configured to nest one type of object folder in another object's structure, you can move on to making a flow.

This video explains the procedure as well as the design intent.  We recommend that you watch it before you attempt to build the flow.

1. Create a new record-triggered flow
2. Choose the CHILD object type and define your triggering condition and click "Done".  (For example, Opportunity, on record created when AccountId is not blank)
   • Be sure to check the box to include an asynchronous path
3. In the asynchronous path, add a Get Records step
   • Set it to point to the parent object.  In our example, Account.
   • Set the condition to pull the Parent object record where the Id matches.  In our example, where Account.Id = AccountId on opportunity.
4. For the next step, add a Decision step to determine if the object is already linked to a SharePoint folder.  If it is, we don't need to set that folder up.  If it is not, we will set it up
   • Use the Account.Sharepoint_Folder_Id__c is null = true logic and name the condition "No Folder"
   • Set the else condition to "Has folder"
5. On the "No Folder" branch, add an Action step.  This is where we will call the function to set up the parent object folder.
   • Choose the sFiles action "Set up SharePoint Folder"
   • Include the objectSettingsLabel and set the value to the name of your Parent object metadata setting. In our example this value is Account
   • Include the recordId and set the value to the ParentId from the object.  In our case the AccountId on the Opportunity
6. Publish the flow.  You are done!

Testing The Flow

1. Navigate to a parent record that is not set up in SharePoint.  In our example, navigate to an account.
2. Create a new child record from related records.  In our example create an opportunity.
3. Now navigate to the child record.  You will now be able to create the folder because the parent record folder was created by the flow.