Consider the following desired folder structure in a SharePoint document library:

This easy-to-navigate structure can easily be built with sFiles. This allows all of an account's related data to be nested neatly within the account folder. This example only shows how to apply this to Account>Opportunity, but the same methodology can be used to add additional objects to the directory structure.

Steps:

1. Start by using the sFiles configuration tool to set up sFiles on your root object (Account, in this example).
   • When it prompts, select or create an Accounts folder.
   • Set the initial folder structure to {"Folders":[{"Name":"Opportunities"}]}. This will create an Opportunities folder under each Account folder automatically.
2. Now use the sFiles configuration tool for the sub object (like Opportunity). When it prompts to select a folder, select the same folder you selected for Accounts. (It will not actually be used in the final config.) No initial folder structure is required.
3. On the child object (like Opportunity), create a new formula field, Root_Folder_Override__c, that concatenates the parent's SharePoint folder Id field, a comma, and the path to a folder that is under the parent folder. For example, in Opportunities, the formula would be Account.sharepoint_folder_id__c + ',Opportunities'.  (This signifies that "Opportunities" underneath the Account folder will be the parent folder of a new Opportunity folder)
4. On the child object App Builder page layout, select the sFiles component and set the Root Id Field API Name property to Root_Folder_Override__c.

Once this configuration is complete:

• When an Account folder is created in sFiles, it will also create an Opportunities folder as a child. 
• When on a child Opportunity and the Create Folder button is clicked, the folder will be created under the Opportunities folder for the parent account.  This can be repeated at many levels of child folders.

Configuration Note: The formula for a child folder in root folder override can include a path as well.  If you want to have a structure like Accounts>Bob's Account>Engineering>Opportunities>Opportunity123, for instance.  To do this, your formula would look like Account.sharepoint_folder_id__c + ',Engineering/Opportunities'

 

What if I have a different site on my parent account?

If using sFiles Enterprise, and linking objects to multiple sites, a few extra steps are necessary to make this set up work. 

Example scenario

Let's assume that the Account object will have a different site than the child Opportunity based on the "Status" field. If the Account's status is "Archived" we will specify a different site than the "Active" status. The Opportunity child will then have to look to the Account's sites to properly be linked. 

In order to set this type of configuration up, we will need a number of new fields:

1. Site Override field on Account. This field will be a formula field that will change the site Id value based on the Status field. For example, If(Status__c = 'Active','Active site Id ','Archived site Id')
2. Document Library Override field on Account. This field will be a formula field that will change the document library Id value based on the Status field. For example, If(Status__c = 'Active','Active document library Id','Archived document library Id')
3. Root Folder Override field on Account. This field will be a formula field that will change the root folder Id value based on the Status field. For example, If(Status__c = 'Active','Active root folder Id','Archived root folder Id')
4. Site Override field on Opportunity. This field will be a formula field that will point to the parent account's Site Override field. Account.Site_Override__c
5. Document Library Override field on Opportunity. This field will be a formula field that will point to the parent account's Document Library Override field. Account.Document_Library_Override__c
6. Root Folder Override field on Opportunity. (Same as documented in the earlier section: concatenates the parent's SharePoint folder Id field, a comma, and the path to a folder )

In the App Builder, define the Site Override, Document Library Override, and Root folder Overrides for both the Account and Opportunity components. 

Now the child object should look to the parent's overrides and correctly route the folders to the appropriate sites.