Skip to content

SharePoint Data Mapping

Data Mapping and Transformation is one of the powerful features of Connect iPaaS. When you create a workflow certain attributes of your trigger application are available to the Action application for data mapping while making API calls.

These attributes can be mapped to the specific attributes of the Action application. This powerful capability not only allows field mapping but it also allows complex transformation using excel style functions to apply hundreds of formulas and operations. The choice of excel style function makes data mapping on Connect iPaaS easy for business users who are already well versed with Microsoft Excel formulas.

Example Scenario with SharePoint Trigger

In the example workflow shown below, SharePoint is the trigger application. You can access the following attributes of the SharePoint event in any of the application actions while designing your workflow.

  • Author - Name of Author
  • Editor - Name of Editor
  • Length - Length of file
  • Level - Depth of file in the directory structure
  • Name - File Name
  • Server Relative URL - is based on the domain (which might be the name of a server) address and always begins with a forward slash. It specifies a complete path from the top-level website to the file name. For example:
/[ sites/] Web_Site/ Lists/ List_Title/ AllItems.aspx

Data Mapping on SharePoint application

Figure 1. Data Mapping on SharePoint Application

As shown in the Figure above, we are mapping parameters from SharePoint "File Added to Document Library" trigger to the ServiceNow Action of creating a new incident. We can create a short description of the ServiceNow incident based on the data attributes of the SharePoint Trigger. In this example, a short description of the incident is constructed as a text string using "Author", "Name", "Server Relative URL" and "Length" attribute of the SharePoint event. We are also using mathematical functions to convert file length to Kilobytes from its default value in bytes.