Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Input

Description

SharePoint Instance Id

Your instance name to use.

Record Id

The record to link this action to.

Server Relative Url (Optional)

The path to the parent folder where the new folder will be created in.

Folder Name

The name of the folder.

🆕 Reset Sharing (Optional)

In addition to creating the folder, reset the sharing back to inherit. Effectively removing all custom sharing rules.

🆕 Skip if no Permission (Optional)

If the running user does not have sharing rights the action will fail. With this enabled the action will be skipped instead. This does not impact the creation of the folder component.

Output

Description

Url to folder

The new server relative url URL to the created folder.

...

Create and Pin Folder

...

Output

Description

Url to folder

The new server relative url URL to the created folder.

...

Pin Folder

...

Input

Description

SharePoint Instance Id

Your instance name to use.

Record Id

The record to link this action to.

Server Relative Url (Optional)

The path to the folder to share.

Salesforce User Id

The id of the Salesforce user. Make sure this user is connected to SharePoint, otherwise Filenize doesn’t know which underlying SharePoint user to use and will cause an error.

Access

The access the user needs on the folder. Possible options are : Full, Design, Edit, Contribute, Read

🆕 Skip if no User Found (Optional)

If the running user does not have a connection with SharePoint the action will fail. With this enabled the action will be skipped instead.

🆕 Skip if no Permission (Optional)

If the running user does not have sharing rights the action will fail. With this enabled the action will be skipped instead.

Output

Description

Url to folder

The relative url URL to the shared folder.

...

Share Folder by SharePoint Id

Sometimes you need to reference users/groups that are not in Salesforce. With this action, you can do so by referencing the id directydirectly.

Input

Description

SharePoint Instance Id

Your instance name to use.

Record Id

The record to link this action to.

Server Relative Url (Optional)

The path to the folder to share.

SharePoint user or group id

The id of the SharePoint user or group.

Access

The access the user needs on the folder. Possible options are : Full, Design, Edit, Contribute, Read

🆕 Skip if no Permission (Optional)

If the running user does not have sharing rights the action will fail. With this enabled the action will be skipped instead.

Output

Description

Url to folder

The relative url URL to the shared folder.

...

🆕 Update Metadata

Input

Description

SharePoint Instance Id

Your instance name to use.

Record Id

The record to link this action to.

Server Relative Url (Optional)

The path to the folder or file to edit.

Property Name

The name of the property in SharePoint to edit.

Value

The new value is to be stored on the folder or file’s property.

...

Input

Description

SharePoint Instance Id

Your instance name to use.

Record Id

The record to link this action to.

Server Relative Url (Optional)

The path to the folder or file to edit.

Mapping Name

The name of the Metadata mapping created in the Filenize configuration.

...

Input

Description

SharePoint Instance Id

Your instance name to use.

Record Id

The record to link this action to.

Server Relative Url (Optional)

The path to the folder to upload the file to.

File Id

The Salesforce file id. Supporting: Attachments, ContentVersions, and ContentDocuments.

Use the folder pinned as the root

If selected the server-relative url URL will start from the pinned folder instead of the root folder.

...

Input

Description

Queueable Group

The queueable group identifier. Multiple queues with the same group will wait after eachother each other to complete.

Output

Description

None

...

Action missing?

Let us know and we will look into it. If the action helps Filenize and is generic, we’ll add it to Filenize short term. Otherwise, we recommend to use using Apex instead.