Create Sharepoint Drive

introduction the cloudfiles create sharepoint drive flow action allows users to automate the creation of new sharepoint drives directly from salesforce this is particularly useful for organisations that need to quickly spin up collaboration spaces for projects, teams, or departments without manual intervention the image below provides an overview of the input parameters and how this action appears in a salesforce flow detailed descriptions of the input and output parameters are provided in the following sections what this action does the create sharepoint drive action simplifies the process of provisioning sharepoint drives through automation scenario for instance, when a new account is created in salesforce, a corresponding sharepoint drive can be automatically generated using this action the drive can be tailored to the specific needs of the account, such as hosting documents, managing tasks, or collaborating with the client’s team this automation eliminates the need for manual setup and ensures consistency across your sharepoint environment note sharepoint has a limitation that a maximum of 2000 drives (or document libraries) can be created within a particular site this flow action will throw an error if the number exceeds beyond that input parameters the following input parameters are required to configure the create sharepoint drive action drive name description input the display name of the drive, reflecting its purpose (e g , marketing team ) drive name is a mandatory input parameter site id description configure and input the site address for setting up the drive site id is a mandatory input parameter content types description define content types for the drive when multiple content types are specified, the order in which content types are provided determines their priority — the first entry takes the highest precedence user defined content types will take preference over the default content types set for the drive disable inherited permissions description set to ' \<font color="#0c121d">true'\</font> to prevent the new drive from inheriting permissions from its parent sharepoint site when enabled, the drive will have no inherited permissions — you can instead define access by grouping users and assigning permissions directly defaults to ' false' (permissions are inherited from the site) site columns description define site columns for the drive how to use site columns ? step 1 create a apex defined variable of apex class cldfs drivecolumn step 2 in an assignment variable assign values for the variable properties (apiname, defaultvalue, label) apiname and defaultvalue are mandatory how to retrieve it ? use the get event details flow action associated with the corresponding event to obtain the id alternatively, if you need to execute queries on a salesforce file later or on demand store the file's processed document id in a custom content version field this allows you to query the document anytime, without relying on the event note the same processed document id can be reused multiple times to reference the document and execute queries as needed site columns are reusable column definitions (fields) that can be associated with a drive to standardise the metadata captured across documents and items if both contenttypes and sitecolumns are added to the action the columns will be ignored output parameters drive id a unique identifier for the created sharepoint drive external url the external url for the newly created sharepoint drive, which can be used to directly access the drive from outside salesforce