# tSharePointInput

Reads files from a SharePoint directory or reads a single SharePoint file using the configured format.

## tSharePointInput Standard properties

These properties are used to configure tSharePointInput running in the Standard Job framework.

The Standard tSharePointInput component belongs to the Business and Cloud families.

The component in this framework is available in all Talend products.

## Basic settings

| Properties | Description |
| --- | --- |
| Connection Component | Reuse a tSharePointConnection component for authentication and connectivity. |
| Property Type | Select the way the connection details<br>will be set.<br><br><ul> <li> <p> <span>Built-In</span>: The connection details will be set                                locally for this component. You need to specify the values for all                                related connection properties manually.</p> </li> <li> <p> <span>Repository</span>: The connection details stored                                centrally in <span><span>Repository</span><abbr> &gt; </abbr><span>Metadata</span></span> will be reused by this component. </p> <p>You need to click                                the <span>[...]</span> button next to it and in the pop-up                                    <span>Repository Content</span> dialog box, select the                                connection details to be reused, and all related connection                                properties will be automatically filled in.</p> </li> </ul> |
| Use an existing connection | Select this check box and in the Component<br>List drop-down list, select the desired connection component to<br>reuse the connection details you already defined. |
| Schema and Edit schema | A schema is a row description. It defines the number of fields<br>(columns) to be processed and passed on to the next component. When you create a Spark<br>Job, avoid the reserved word line when naming the<br>fields.<br><br><ul> <li> <p> <span>Built-In</span>: You create and store the schema locally for this component                only.</p> </li> <li> <p> <span>Repository</span>: You have already created the schema and stored it in the                Repository. You can reuse it in various projects and Job designs.</p> </li> </ul><br><br>Click Edit schema to make changes to<br>the schema. If you make changes, the schema automatically becomes built-in.<br><br><ul> <li> <p> <span>View schema</span>: choose this                option to view the schema only.</p> </li> <li> <p> <span>Change to built-in property</span>:                choose this option to change the schema to <span>Built-in</span> for local changes.</p> </li> <li> <p> <span>Update repository connection</span>:                choose this option to change the schema stored in the repository and decide whether                to propagate the changes to all the Jobs upon completion.</p> <p>If you just want to                propagate the changes to the current Job, you can select <span>No</span> upon completion and choose this schema metadata                again in the <span>Repository Content</span>                window.</p> </li> </ul><br><br>This component offers the advantage of the<br>dynamic schema feature. This allows you to retrieve unknown columns from source<br>files or to copy batches of columns from a source without mapping each column<br>individually. For further information about dynamic schemas, see [Dynamic schema](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/dynamic-schema).<br><br>This<br>dynamic schema feature is designed for the purpose of retrieving unknown columns of a<br>table and is recommended to be used for this purpose only; it is not recommended for the<br>use of creating tables. |
| Guess schema | Click this button to infer the schema from the file. If your file contains a<br>header, click Set header first and configure it before<br>guessing the schema. |
| Site | Specify or select the SharePoint site. |
| Path | Enter the path of the SharePoint directory to read. |
| File format | Select the format used to read the files. Supported formats are CSV, Excel, Avro, and JSON. |
| Format configuration | Configure the selected file format (separators, encoding, header, etc). |
| Input mode | Read all files in a directory that match the configured format, starting with the first file, or read a single file. |

## Advanced settings

| Properties | Description |
| --- | --- |
| tStatCatcher Statistics | Select this checkbox to collect the log data at the component<br>level. |
| Escape character and Quote<br>character | <ul> <li> <span>Escape character</span>: Enter the character you want to                           be used as the escape character. The escape character used by default is                              <kbd>\</kbd>.</li> <li> <span>Quote character</span>: Enter the character you want to                           be used as the quote character. The quote character used by default is                              <kbd>"</kbd>.</li> </ul><br><br>These options are available if you select CSV from the<br>File format list in the Basic<br>settings view. |
| Skip empty lines | Select this option to prevent the component from generating an output record<br>when the line of the CSV file is empty.<br><br>This option is available if you select<br>CSV from the File format list<br>in the Basic settings view. |
| Define a value for 'null' | By default, the CSV format can only handle empty strings, not null<br>values.<br><br>Select this option to enter a string that represent null values in<br>the CSV file in the Value that represent ‘null’ field.<br>When this value is found for a column or a row, this will generate a null value<br>in the generated record.<br><br>This option is available if you select<br>CSV from the File format list<br>in the Basic settings view. |

## Usage

| Usage guidance | Description |
| --- | --- |
| Usage rule | This component can reuse tSharePointConnection. No Close component is needed. |