# Configuration ## Content To create a configuration for a CSV source from either a local or HTTP location, you need to configure the tables in the database. Each table should have four sections: **SelectOperation**, **InsertOperation**, **UpdateOperation**, and **DeleteOperation.** * The **SelectOperation** section extracts data for the select statement and generates the schema of the table. In the **SelectOperation** section, you should configure the Uri, method, and list of fields in the table. * The **InsertOperation** section builds an insert request to send to the server. In the **InsertOperation** section, you should configure the Uri, method, and list of fields to build the insert request body. * The **UpdateOperation** section builds an update request to send to the server. In the **UpdateOperation** section, you should configure the Uri, method, and list of fields to build the update request body. * The **DeleteOperation** section builds a delete request to send to the server. In the **DeleteOperation** section, you should configure the Uri format, method, and parameters to build the request Uri. In the following example, the \ tag is used to configure each table in the database and divide it into the sections discussed above. To enable CRUD operations for an HTTP/HTTPS CSV source, the provider offers custom API configurations through a configuration file. The API configuration file should be in XML format and should include the configuration for all CRUD operations supported by the CSV source. ## Supported Data Types The supported data types for Column in the Api Config file are: | **Type** | **Description** | | --- | --- | | byte | Represents an unsigned 8-bit integer value. | | sbyte | Represents a signed 8-bit integer value. | | short | Represents a signed 16-bit integer value. | | ushort | Represents an unsigned 16-bit integer value. | | int | Represents a signed 32-bit integer value. | | uint | Represents an unsigned 32-bit integer value. | | long | Represents a signed 64-bit integer value. | | ulong | Represents an unsigned 64-bit integer value. | | float | Represents a single-precision floating-point number. | | double | Represents a double-precision floating-point number. | | decimal | Represents a high-precision decimal floating-point number. | | char | Represents a Unicode character. | | bool | Represents a Boolean value indicating true or false. | | string | Represents a sequence of characters. | | DateTime | Represents a date and time value. | | TimeSpan | Represents a time interval. | | DateTimeOffset | Represents a date and time value with an offset from UTC. | | Guid | Represents a globally unique identifier. | Below is an example of an XML API configuration file: ```XML

"GET_url"/Album Get AlbumId Title ArtistId "POST_url"/Album Post AlbumId Title ArtistId "PUT_url"/Album PUT AlbumId Title ArtistId "DELETE_url"/api/Album/{Param1} DELETE AlbumId

"GET_url"/Customer Get CustomerId FirstName "POST_url"/api/Customer Post CustomerId FirstName "PUT_url"/Customer PUT CustomerId FirstName "DELETE_url"/Customer/{Param1} DELETE CustomerId

``` The API configuration file can be passed to the provider through the [API Config File](/componentone/api/services/online-dataconnector/dotnet-standard-api/C1.AdoNet.CSV/C1.AdoNet.CSV.C1CSVConnection.ApiConfigFile.html) property in the connection string: ```csharp static string csvConnectionString = $"Uri='';API Config File='api_config.xml'"; ```