# Defining data source details In the **Details** tab, under **Properties**, ![](/files/-M2CHasO5jwv__T34Wz3) Complete the following **details** : | **Property** | **Description** | | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Name**\* | A unique name used to refer to the datasource object within the application | | **Table Name**\* | The name of the database object containing the data; for example, name of the Table, View or REST API | | **API Name** | The name of the stored procedure, if any, that is used to perform DML operations | | **Object Type** | The type of the underlying data source | | **Object Connection Code** |

A connection code for connecting to different schemas/databases.

Note: The object connection details of these schemas/databases must be defined in the Setup page. If you are using the default application schema under the current subdomain, you must not select any Object Connection Code.

| | **Object Handler Class** | The class name of the custom java code, if any, that required to access the datasource | | **Enable logging** |

Select Yes to enable logging of database operations.

Note: This is useful for debugging the pre-query, post query or server-side validation scripts.

| If applicable, select the following **checkboxes** : | **Name** | **Description** | | -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Active** |

Indicates that the datastore is active.

If inactivated, any UI component, that is bound to the object, will throw an error while trying to access the object.

| | **UseAPI** | Indicates the use of the APIs for standard DML operations | | **Call Post Query** | Indicates that the defined post query will be invoked | | **Skip Query For Updates** | Indicates that the update query operation, if any, will be skipped for the data source | | **Email On Insert** | Sends email notifications when the user performs an insert operation | | **Email On Update** | Sends email notifications when the user performs an update operation | | **Email On Delete** | Sends email notifications when the user performs a delete operation | | **Confirmation Enabled** | Indicates that a confirmation message will pop up in the **UI** before an action is to be performed. | Click **Save**. The datasource is created and can be accessed from the **Manage Datasources**. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.cloudio.io/creating-datasources/working-with-datasources/creating-a-data-source/defining-data-source-details.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.