Read Excel Table > Runtime Template > SharePoint

Specifies the data source for your runtime template on SharePoint in the Read Excel Table activity.

Figure: Runtime Template Configuration screen (SharePoint)

Runtime Template Configuration screen SharePoint

Examples

Prerequisites

Good to Know

  • Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

How to Start

Fields

Field NameDefinition

SharePoint

Function:
Specifies the access token that connects to your SharePoint site.
Accepted Values:
A list of access tokens configured for your environment.
Default Value:
None
Example:
Refer to:

Create Add Token icon

Opens this Screen:
Access Token for SharePoint
Function of this Screen:
Configure an access token to connect to SharePoint.
Example:
Refer to:

Site

Function:
Specifies the URL for your SharePoint site.
Accepted Values:
A valid SharePoint site URL.
Default Value:
None
Accepts Process Data Variables:
Yes
Example:

Document Library

Function:
Specifies the name of the SharePoint document library.
Accepted Values:
A valid SharePoint document library name.
Default Value:
None
Accepts Process Data Variables:
Yes

File Path

Function:
Specifies the path of the file.
Accepted Values:
  • Choose File Path - Specifies an absolute path for the file.
  • Dynamic File Path - Specifies a process data variable that stores the path for the file.
Default Value:
Dynamic File Path
Accepts Process Data Variables:
Yes
Limitations:

Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?