- Trifacta® Enterprise Edition
- Trifacta Professional Edition
- Trifacta Premium
You can create connections to your Microsoft SharePoint instance from Trifacta®.
You can create connections to:
- SharePoint On-Premises installations in your enterprise infrastructure
- SharePoint Online
NOTE: This connection supports reading from and writing to SharePoint lists.
For more information on Microsoft SharePoint, see https://www.microsoft.com/en-us/microsoft-365/sharepoint/collaboration.
NOTE: During normal selection or import of an entire table, you may encounter an error indicating a problem with a specific column. Since some tables require filtering based on a particular column, data from them can only be ingested using custom SQL statements. In this case, the problematic column can be used as a filter in the WHERE clause of a custom SQL statement to ingest the table. NOTE: For filtering date columns, this connection type supports a set of literal functions on dates. You can use these to reduce the volume of data extracted from the database using a custom SQL query. For more information, see the
pg_dateliteralfunctions.htm page in the driver documentation for this connection type.
NOTE: During normal selection or import of an entire table, you may encounter an error indicating a problem with a specific column. Since some tables require filtering based on a particular column, data from them can only be ingested using custom SQL statements. In this case, the problematic column can be used as a filter in the WHERE clause of a custom SQL statement to ingest the table.
NOTE: For filtering date columns, this connection type supports a set of literal functions on dates. You can use these to reduce the volume of data extracted from the database using a custom SQL query. For more information, see the
- Single Sign-On (SSO) is not supported.
- Column names are not validated on publishing.
- The SharePoint connection uses SharePoint APIs. As a result, transaction management and rollbacks are not supported.
- No schema validation is performed as part of writing results to SharePoint Lists.
The logged-in user must have required access to the tables and schema.
To create this connection, in the Connections page , select the Applications tab. Click the SharePoint card. See Connections Page.
Modify the following properties as needed:
Enter the URL for your SharePoint Site or sub-site. Example value:
Product edition of SharePoint in use:
Username to use to connect to SharePoint.
|Password||Password associated with the above username.|
After you have defined the SharePoint Edition, credentials, and connection string, you can validate those credentials.
|Additional Connect String Options|
Apply any connection string options that are part of your authentication to SharePoint.
A default string has been provided for you. For more information, see below.
|Default Column Data Type Inference|
|Connection Name||Display name of the connection|
|Connection Description||Description of the connection, which appears in the application.|
Connect string options
The following connection string is provided for you:
|AutoCache||When enabled, the connection leverages any data that is automatically cached for each table. The default is |
When enabled, table metadata can be retrieved from the SharePoint cache. The default is
|CacheTolerance||This setting defines the duration in hours that objects are permitted to live in the cache. The default is |
This setting defines the number of seconds that a query to the SharePoint database is allowed to run without a response. The SharePoint default timeout is
The default value in the Connect String Options is
|ShowPredefinedColumns||When enabled, users of the connection are permitted to view the columns that are created with the table, such as Created By and Modified By columns. The default is |
For more information, see http://cdn.cdata.com/help/RSG/jdbc/Connection.htm.
You can import datasets from SharePoint. See Database Browser.
Using SharePoint Connections
This section describes how you interact through Trifacta® with your SharePoint Lists.
- SharePoint is a content management system for sharing and collaborating across the enterprise. For more information, see https://sharepoint.microsoft.com.
In SharePoint, data is stored in an object called a List. Lists can also include non-tabular data.
NOTE: Non-tabular data and some SharePoint List columns are converted to strings on import. For more information, see SharePoint Data Type Conversions.
Uses of SharePoint
Trifacta can use SharePoint for the following tasks:
- Import datasets by reading from SharePoint Lists.
Write to SharePoint Lists with your job results.
Before You Begin Using SharePoint
Read Access: Your SharePoint administrator must configure read permissions.
Write Access: You can write and publish jobs results to SharePoint.
SSL is available over HTTPS for SharePoint connections.
Storing data in SharePoint
Your SharePoint administrator should provide database access for storing datasets. Users should know where shared data is located and where personal data can be saved without interfering with or confusing other users.
NOTE: Trifacta does not modify source data in SharePoint. Datasets sourced from SharePoint are read without modification from their source locations.
Reading from SharePoint
You can create a Trifacta dataset from a List stored in SharePoint.
NOTE: Reading data is supported for SharePoint Lists only.
For more information, see Database Browser.
Writing to SharePoint
You can write back data to SharePoint using one of the following methods:
Job results can be written directly to SharePoint as part of the normal job execution. Create a new publishing action to write to SharePoint. See Run Job Page.
- For more information on how data is converted to SharePoint, see SharePoint Data Type Conversions.
Data Validation issues:
NOTE: Some Trifacta data types do not map exactly to SharePoint List data types. These differences may appear when writing to a new SharePoint List. For more information, see SharePoint Data Type Conversions.
NOTE: Column name validation is not supported.
- No validation is performed for the connection and any required permissions during job execution. So, you can be permitted to launch your job even if you do not have sufficient connectivity or permissions to access the data. The corresponding publish job fails at runtime.
- Prior to publication, no validation is performed on whether a target is a table or a view, so the job that was launched fails at runtime.
Supported versions: n/a
- Read: Supported
- Write: Supported
This page has no comments.