> ## Documentation Index > Fetch the complete documentation index at: https://docs.maia.ai/llms.txt > Use this file to discover all available pages before exploring further. # SharePoint Query export const maia = "Maia"; export const componentName_0 = "SharePoint Query" export const ComponentMetadata = ({warehouses, unsupportedWarehouses = [], componentType, connectionInputs, connectionOutputs}) => { const allWarehouses = [...warehouses.map(w => ({ name: w, supported: true })), ...unsupportedWarehouses.map(w => ({ name: w, supported: false }))]; return

Project Availability	{allWarehouses.map((w, i) => {w.name} {w.supported ? '✅' : '❌'} )}
Component Type	{componentType}
Connection Inputs	{connectionInputs}
Connection Outputs	{connectionOutputs}

; }; The {componentName_0} component uses the Connect and Configure parameters to create a table of data, which is then stored in your preferred storage location (Snowflake, Databricks, or Amazon Redshift). You *do not* need to use the Create Table component when using this component, as each time the {componentName_0} component runs, the target table is recreated, dropping any existing table of the same name. Once the component has run once, you can use transformation pipelines to transform your data to fit your business requirements. This component's driver currently supports: * Windows SharePoint Services 3.0 * Microsoft Office SharePoint Server 2007 * SharePoint Server 2010 * SharePoint Server 2013 * SharePoint Server 2016 * SharePoint Online If the component requires access to a cloud provider (AWS, Azure, or Google Cloud), it will use credentials as follows: * If using [Matillion Full SaaS](/docs/guides/runner-overview#matillion-full-saas): The component will use the [cloud credentials](/docs/guides/cloud-credentials) associated with your environment to access resources. * If using [Hybrid SaaS](/docs/guides/runner-overview#hybrid-saas): By default the component will inherit the agent's execution role (service account role). However, if there are [cloud credentials](/docs/guides/cloud-credentials) associated to your environment, these will overwrite the role. Microsoft removed NTLM authentication support on **January 31, 2026** and Basic authentication support on **May 1, 2026** for SharePoint Online. If you're connecting to SharePoint Online via SOAP using Basic or NTLM credentials, you must migrate to the REST service type with Azure AD OAuth immediately, as these authentication methods are no longer supported. SOAP authentication remains supported for SharePoint On-Premise. For more information, see the [CData driver changelog](https://cdn.cdata.com/help/RSM/jdbc/pg_changelog.htm). This component is potentially destructive. If the target table undergoes a change in structure, it will be recreated. Otherwise, the target table is truncated. Setting the load option **Recreate Target Table** to **Off** will prevent both recreation and truncation. Do not modify the target table structure manually. *** ## Video example

</p> *** ## Properties Reference material is provided below for the Connect, Configure, Destination, and Advanced Settings properties. <ResponseField name="Name" type="string" required> A human-readable name for the component. </ResponseField> ### Connect <ResponseField name="Service Type" type="drop-down" required> The type of API that the component connects to. Choose **REST** to use an OAuth connection (required for SharePoint Online), or **SOAP** to use a username and password (SharePoint On-Premise only). SOAP is not supported for SharePoint Online. </ResponseField> {/*  */} <ResponseField name="Authentication" type="drop-down" required> (REST only) Choose your OAuth connection from the drop-down menu. Click **Manage** to navigate to the **OAuth connections** list to review OAuth connections and to add new connections. Read [OAuth](/docs/guides/oauth) to learn how to create an OAuth connection. To set up a new OAuth profile: 1. Click **Add OAuth connection**. 2. Enter a unique, descriptive OAuth name. 3. Select your provider. In this case, **SharePoint**. 4. Set the authentication type to **OAuth 2.0 Authorization Code Grant**. This uses Azure AD to authenticate. 5. Enter your SharePoint root URL. For example, `https://companyname.sharepoint.com`. 6. Click **Authorize**. A new browser tab will open to log in to `https://login.microsoftonline.com/`. 7. Enter your username and click **Accept**. 8. The browser tab closes and you're returned to {maia}. The **OAuth** tab will be open, displaying your newly created SharePoint OAuth connection in the **OAuth connections** list. You may need to close and reopen the parameter for your new OAuth connection to propagate. 9. Return to the **Authentication** parameter in your SharePoint Query component and locate your new OAuth profile in the drop-down menu. If the profile has not propagated, click out of the dialog and then try again. </ResponseField> {/*  */} <ResponseField name="User" type="string" required> (SOAP only—SharePoint On-Premise only) Enter a valid SharePoint username. </ResponseField> {/*  */} <ResponseField name="Password" type="drop-down" required> (SOAP only—SharePoint On-Premise only) Choose the secret definition that represents your credentials for this connector. If you have not already saved your credentials for this connector as a secret definition, click **Add secret** to create a secret definition representing these credentials. Read [Secrets and secret definitions](/docs/guides/secrets-and-secret-definitions) for details about creating a secret definition. </ResponseField> {/*  */} <ResponseField name="URL" type="string" required> (SOAP only—SharePoint On-Premise only) The URL is the web address you use to log in to your SharePoint account. For example, `https://companyname.sharepoint.com`. </ResponseField> {/*  */} <ResponseField name="SharePoint Edition" type="drop-down" required> Select your edition of SharePoint. </ResponseField> {/*  */} <ResponseField name="Connection Options" type="column editor"> `Connection Options` = *column editor* * **Parameter:** A JDBC parameter supported by the database driver. The available parameters are explained in the data model. Manual setup is not usually required, since sensible defaults are assumed. * **Value:** A value for the given parameter. Click the **Text Mode** toggle at the bottom of the **Connection Options** dialog to open a multi-line editor that lets you add items in a single block. For more information, read [Text mode](/docs/guides/components-overview#component-properties). To use [grid variables](/docs/guides/grid-variables), select the **Use Grid Variable** checkbox at the bottom of the **Connection Options** dialog. <Note> To query subsites, in the `Connection Options` property, enter `URL` as a parameter, with your site URL as the value. This must be the full URL, e.g. `https://companyname.sharepoint.com/sitename` (for classic/root sites) or `https://companyname.sharepoint.com/sites/sitename` (for modern site collections). </Note> </ResponseField> ### Configure <ResponseField name="Basic/Advanced Mode" type="drop-down" required> * **Basic:** This mode builds a query for you using settings from the **Data Source**, **Data Selection**, **Data Source Filter**, **Combine Filters**, and **Limit** parameters. In most cases, this mode is sufficient. * **Advanced:** This mode requires you to write an SQL-like query to call data from the service you're connecting to. The available fields and their descriptions are documented in the data model. There are some special pseudo columns that can form part of a query filter, but are not returned as data. This is fully described in the data model. </ResponseField> {/*  */} <ResponseField name="SQL Query" type="code editor" required> This is an SQL-like SELECT query, written in the SQL accepted by your cloud data warehouse. Treat collections as table names, and fields as columns. Only available in **Advanced** mode. </ResponseField> {/*  */} <ResponseField name="Data Source" type="drop-down" required> Select a single data source to be extracted from the source system and loaded into a table in the destination. The source system defines the data sources available. Use multiple components to load multiple data sources. </ResponseField> {/*  */} <ResponseField name="Data Selection" type="dual listbox" required> Select one or more columns to return from the query. The columns available are dependent upon the data source selected. Move columns left-to-right to include in the query. To use [grid variables](/docs/guides/grid-variables), select the **Use Grid Variable** checkbox at the bottom of the **Data Selection** dialog. </ResponseField> {/*  */} <ResponseField name="Data Source Filter" type="column editor"> Define one or more filter conditions that each row of data must meet to be included in the load. * **Input Column:** Select an input column. The available input columns vary depending upon the data source. * **Qualifier:** * **Is:** Compares the column to the value using the comparator. * **Not:** Reverses the effect of the comparison, so "Equals" becomes "Not equals", "Less than" becomes "Greater than or equal to", etc. * **Comparator:** Choose a method of comparing the column to the value. Possible comparators include: "Equal to", "Greater than", "Less than", "Greater than or equal to", "Less than or equal to", "Like", "Null". Not all data sources support all comparators. * **Value:** The value to be compared. Click the **Text Mode** toggle at the bottom of the dialog to open a multi-line editor. For more information, read [Text mode](/docs/guides/components-overview#component-properties). </ResponseField> {/*  */} <ResponseField name="Combine Filters" type="drop-down" required> The data source filters you have defined can be combined using either **And** or **Or** logic. If **And**, then all filter conditions must be satisfied to load the data row. If **Or**, then only a single filter condition must be satisfied. The default is **And**. If you have only one filter, or no filters, this parameter is essentially ignored. </ResponseField> {/*  */} <ResponseField name="Row Limit" type="integer"> Set a numeric value to limit the number of rows that are loaded. The default is an empty field, which will load all rows. </ResponseField> ### Destination Select your cloud data warehouse. <Tabs> <Tab title="Snowflake"> <ResponseField name="Type" type="drop-down" required> * **Standard:** The data will be staged in your storage location before being loaded into a table. This is the only setting currently available. </ResponseField> {/*  */} <ResponseField name="Primary Keys" type="dual listbox"> Select one or more columns to be designated as the table's primary key. </ResponseField> {/*  */} <ResponseField name="Warehouse" type="drop-down" required> The Snowflake warehouse used to run the queries. The special value `[Environment Default]` uses the warehouse defined in the environment. Read [Overview of Warehouses](https://docs.snowflake.com/en/user-guide/warehouses-overview.html) to learn more. </ResponseField> {/*  */} <ResponseField name="Database" type="drop-down" required> The Snowflake database. The special value `[Environment Default]` uses the database defined in the environment. Read [Databases, Tables and Views - Overview](https://docs.snowflake.com/en/guides-overview-db) to learn more. </ResponseField> {/*  */} <ResponseField name="Schema" type="drop-down" required> The Snowflake schema. The special value `[Environment Default]` uses the schema defined in the environment. Read [Database, Schema, and Share DDL](https://docs.snowflake.com/en/sql-reference/ddl-database.html) to learn more. </ResponseField> {/*  */} <ResponseField name="Target Table" type="string" required> The name of the table to be created in your Snowflake database. This table will be recreated and will drop any existing table of the same name. You can use a [Table Input](/docs/components/table-input) component in a transformation pipeline to access and transform this data after it has been loaded. </ResponseField> {/*  */} <ResponseField name="Stage" type="drop-down" required> Select a managed stage. The special value, \[Custom], will create a stage "on the fly" for use solely within this component. </ResponseField> {/*  */} <ResponseField name="Stage Platform" type="drop-down" required> Choose where the data is staged before being loaded into your Snowflake table using the drop-down menu. * **Existing Amazon S3 Location:** Activates the **S3 Staging Area** property, allowing users to specify a custom staging area on Amazon S3. The **Stage Authentication** property is also activated, letting users select a method of authenticating the data staging. * **Existing Azure Blob Storage Location:** Activates the **Storage Account** and **Blob Container** properties, allowing users to specify a custom staging location on Azure. The **Stage Authentication** property is also activated, letting users select a method of authenticating the data staging. * **Existing Google Cloud Storage Location:** Activates the **Storage Integration** and **GCS Staging Area** properties, allowing users to specify a custom staging area within Google Cloud Storage. * **Snowflake Managed:** Create and use a temporary internal stage on Snowflake for staging the data. This stage, along with the staged data, will cease to exist after loading is complete. This is the default setting. </ResponseField> {/*  */} <ResponseField name="Stage Authentication" type="drop-down" required> Select an authentication method for data staging. Only available when **Stage Platform** is set to either **Existing Amazon S3 Location** or **Existing Azure Blob Storage Location**. * **Credentials:** Uses the credentials configured in the environment. If no credentials have been configured, an error will occur. * **Storage Integration:** Use a Snowflake storage integration to authentication data staging. </ResponseField> {/*  */} <ResponseField name="Storage Integration" type="drop-down" required> Select a Snowflake storage integration from the drop-down list. Storage integrations are required to permit Snowflake to read data from and write to your cloud storage location and must be [set up in advance of selection](https://docs.snowflake.com/en/sql-reference/sql/create-storage-integration). </ResponseField> {/*  */} <ResponseField name="S3 Staging Area" type="drop-down" required> Select an S3 bucket for temporary storage. Ensure your access credentials have S3 access and permission to write to the bucket. The temporary objects created in this bucket will be removed again after the load completes. </ResponseField> {/*  */} <ResponseField name="Storage Account" type="drop-down" required> Select a storage account with your desired blob container to be used for staging the data. For more information, read [Storage account overview](https://learn.microsoft.com/en-us/azure/storage/common/storage-account-overview). </ResponseField> {/*  */} <ResponseField name="Blob Container" type="drop-down" required> Select a Blob container to be used for staging the data. For more information, read [Introduction to Azure Blob storage](https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction). </ResponseField> {/*  */} <ResponseField name="GCS Staging Area" type="drop-down" required> The URL and path of the target Google Cloud Storage bucket to be used for staging the queried data. </ResponseField> </Tab> <Tab title="Databricks"> <ResponseField name="Catalog" type="drop-down" required> Select a [Databricks Unity Catalog](https://docs.databricks.com/en/data-governance/unity-catalog/index.html). The special value `[Environment Default]` uses the catalog defined in the environment. Selecting a catalog will determine which databases are available in the next parameter. </ResponseField> {/*  */} <ResponseField name="Schema (Database)" type="drop-down" required> The Databricks schema. The special value `[Environment Default]` uses the schema defined in the environment. Read [Create and manage schemas](https://docs.databricks.com/en/data-governance/unity-catalog/create-schemas.html) to learn more. </ResponseField> {/*  */} <ResponseField name="Table" type="string" required> The name of the table to be created in your Databricks schema. This table will be recreated and will drop any existing table of the same name. You can use a [Table Input](/docs/components/table-input) component in a transformation pipeline to access and transform this data after it has been loaded. </ResponseField> {/*  */} <ResponseField name="Stage Platform" type="drop-down" required> Choose where the data is staged before being loaded into your Databricks table using the drop-down menu. * **AWS S3:** Lets users specify a custom staging area on Amazon S3. * **Azure Blob:** Lets users specify a custom staging area on Azure Blob storage. * **Personal Staging (deprecated):** Uses a Databricks personal staging location. This option has been deprecated by Databricks. * **Volume:** Use a pre-existing [Databricks volume](https://docs.databricks.com/en/sql/language-manual/sql-ref-volumes.html) to stage your data. Only external volumes are available. </ResponseField> {/*  */} <ResponseField name="S3 Staging Area" type="drop-down" required> Select an S3 bucket for temporary storage. The temporary objects created in this bucket will be removed again after the load completes. </ResponseField> {/*  */} <ResponseField name="Storage Account" type="drop-down" required> Select a storage account with your desired Blob container to be used for staging the data. For more information, read [Storage account overview](https://learn.microsoft.com/en-us/azure/storage/common/storage-account-overview). </ResponseField> {/*  */} <ResponseField name="Blob Container" type="drop-down" required> Select a Blob container to be used for staging the data. For more information, read [Introduction to Azure Blob storage](https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction). </ResponseField> {/*  */} <ResponseField name="Volume" type="drop-down" required> Select a [Databricks volume](https://docs.databricks.com/en/sql/language-manual/sql-ref-volumes.html). </ResponseField> </Tab> <Tab title="Amazon Redshift"> <ResponseField name="Type" type="drop-down" required> * **Standard:** The data will be staged in your storage location before being loaded into a table. This is the only setting currently available. </ResponseField> {/*  */} <ResponseField name="Schema" type="drop-down" required> Select the table schema. The special value `[Environment Default]` uses the schema defined in the environment. For more information on using multiple schemas, read [Schemas](https://docs.aws.amazon.com/redshift/latest/dg/r_Schemas_and_tables.html). </ResponseField> {/*  */} <ResponseField name="Target Table" type="string" required> The name of the table to be created in your Amazon Redshift schema. This table will be recreated and will drop any existing table of the same name. You can use a [Table Input](/docs/components/table-input) component in a transformation pipeline to access and transform this data after it has been loaded. </ResponseField> {/*  */} <ResponseField name="S3 Staging Area" type="S3 bucket" required> Select an S3 bucket for temporary storage. The temporary objects created in this bucket will be removed again after the load completes. </ResponseField> {/*  */} <ResponseField name="Distribution Style" type="drop-down" required> Table distribution is critical to good performance. Read the [Distribution styles](https://docs.aws.amazon.com/redshift/latest/dg/c_choosing_dist_sort.html) documentation for more information. * **All:** Copy rows to all nodes in the Redshift cluster. * **Auto:** (Default) Allow Redshift to manage your distribution style. * **Even:** Distribute rows around the Redshift cluster evenly. * **Key:** Distribute rows around the Redshift cluster according to the value of a key column. </ResponseField> {/*  */} <ResponseField name="Distribution Key" type="drop-down" required> This parameter is only available when **Distribution Style** is set to **Key**. Select a column from the input that should be set as the table's distribution key. This column should be chosen carefully, as it will determine how the data is distributed around the Redshift cluster. </ResponseField> {/*  */} <ResponseField name="Sort Key" type="dual listbox" required> Sort keys are critical to good performance. Read [Working with sort keys](https://docs.aws.amazon.com/redshift/latest/dg/t_Sorting_data.html) for more information. This property is optional, and lets you specify one or more columns from the input that should be set as the table's sort key. </ResponseField> {/*  */} <ResponseField name="Sort Key Options" type="drop-down" required> Decide whether the sort key is of a compound or interleaved variety. </ResponseField> {/*  */} <ResponseField name="Primary Key" type="dual listbox" required> Select one or more columns to be designated as the table's primary key. </ResponseField> </Tab> </Tabs> ### Advanced Settings <Tabs> <Tab title="Snowflake"> <ResponseField name="Load Options" type="multiple drop-downs" required> * **Clean Staged Files:** Destroy staged files after loading data. Default is **On**. * **String Null is Null:** Converts any strings equal to null into a null value. This is case-sensitive and only works with entirely lower-case strings. Default is **Off**. * **Recreate Target Table:** Choose whether the component recreates its target table before the data load. If **Off**, the existing table will be used. Default is **On**. * **File Prefix:** Give staged file names a prefix of your choice. Default is empty (no prefix). * **Trim String Columns:** Remove leading and trailing characters from a string column. Default is **On**. * **Compression Type:** Set the compression type to either **gzip** (default) or **None**. </ResponseField> </Tab> <Tab title="Databricks"> <ResponseField name="Load Options" type="multiple drop-downs" required> * **Clean Staged Files:** Destroy staged files after loading data. Default is **On**. * **String Null is Null:** Converts any strings equal to null into a null value. This is case-sensitive and only works with entirely lower-case strings. Default is **Off**. * **Recreate Target Table:** Choose whether the component recreates its target table before the data load. If **Off**, the existing table will be used. Default is **On**. * **File Prefix:** Give staged file names a prefix of your choice. Default is empty (no prefix). * **Compression Type:** Set the compression type to either **gzip** (default) or **None**. </ResponseField> </Tab> <Tab title="Amazon Redshift"> <ResponseField name="Load Options" type="multiple drop-downs" required> * [Comp Update:](https://docs.aws.amazon.com/redshift/latest/dg/copy-parameters-data-load.html#copy-compupdate) Apply automatic compression to the target table. Default is On. * [Stat Update:](https://docs.aws.amazon.com/redshift/latest/dg/copy-parameters-data-load.html#copy-statupdate) Automatically update statistics when filling a table. Default is On. * **Clean S3 Objects:** Automatically remove UUID-based objects on the S3 bucket. Default is On. * **String Null is Null:** Converts any strings equal to "null" into a null value. This is case-sensitive and only works with entirely lower-case strings. Default is On. * **Recreate Target Table:** Choose whether the component recreates its target table before the data load. If Off, the existing table will be used. Default is On. * **File Prefix:** Give staged file names a prefix of your choice. * **Compression Type:** Set the compression type to either gzip (default) or None. </ResponseField> </Tab> </Tabs> {/*  */} <ResponseField name="Encryption" type="drop-down" required> Decide how the files are encrypted inside the S3 bucket. This property is available when using an existing Amazon S3 location for staging. * **None:** No encryption. * **SSE KMS:** Encrypt the data according to a key stored on KMS. Read [AWS Key Management Service (AWS KMS)](https://aws.amazon.com/kms/) to learn more. * **SSE S3:** Encrypt the data according to a key stored on an S3 bucket. Read [Using server-side encryption with Amazon S3-managed encryption keys (SSE-S3)](https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingServerSideEncryption.html) to learn more. </ResponseField> {/*  */} <ResponseField name="KMS Key ID" type="drop-down" required> The ID of the KMS encryption key you have chosen to use in the **Encryption** property. </ResponseField> {/*  */} <ResponseField name="Auto Debug" type="drop-down" required> Choose whether to automatically log debug information about your load. These logs can be found in the task history and should be included in support requests concerning the component. Turning this on will override any debugging connection options. </ResponseField> {/*  */} <ResponseField name="Debug Level" type="drop-down" required> The level of verbosity with which your debug information is logged. Levels above 1 can log huge amounts of data and result in slower execution. These logs can be found in the **Message** field of the [task details](/docs/guides/designer-ui-basics#task-history-tab) after pipeline execution and should be included in support requests concerning the component. 1. Will log the query, the number of rows returned by it, the start of execution and the time taken, and any errors. 2. Will log everything included in Level 1, plus cache queries and additional information about the request, if applicable. 3. Will additionally log the body of the request and the response. 4. Will additionally log transport-level communication with the data source. This includes SSL negotiation. 5. Will additionally log communication with the data source, as well as additional details that may be helpful in troubleshooting problems. This includes interface commands. </ResponseField> ## Migrating from SOAP to REST (SharePoint Online) If you're currently using the SOAP service type to connect to SharePoint Online with Basic or NTLM credentials, you must switch to REST with Azure AD OAuth immediately, as Microsoft's deprecation deadlines have passed. 1. Set **Service Type** to **REST**. 2. Create a new Azure AD OAuth connection. See the **Authentication** parameter in the [Connect](#connect) section for step-by-step instructions. 3. Remove any stored **User**, **Password**, and **URL** values—these parameters aren't used by the REST service type. 4. Run a test job to confirm connectivity. *** ## Data model The JDBC driver for this component models SharePoint APIs as relational tables, views, and stored procedures, which are documented in the data model. You'll also find API limitations and requirements. The connection option `SupportEnhancedSQL` is set to `true` by default and typically circumvents most API limitations. * [SharePoint REST API views](https://cdn.cdata.com/help/RSG/jdbc/pg_restallviews.htm) * [SharePoint SOAP API tables](https://cdn.cdata.com/help/RSG/jdbc/pg_soapalltables.htm) (SharePoint On-Premise only) * [SharePoint SOAP API views](https://cdn.cdata.com/help/RSG/jdbc/pg_soapallviews.htm) (SharePoint On-Premise only) * [Connection options](https://cdn.cdata.com/help/RSG/jdbc/Connection.htm)