> For the complete documentation index, see [llms.txt](https://docs.appstrategy.com/apprules-r-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appstrategy.com/apprules-r-documentation/platform/platform-features/system-settings/data-sources/connection-settings/files/delimited-file.md). # Delimited File The following are the properties for Delimited File metadata. Note that you can connect to Delimited or Csv Files directly through the activity or action in your project (if the file fields can be defined from a unique source). You only need to define the metadata if you want to reuse the definition in future projects or if the fields are not derived from an existing data source (for example to specify a csv target mixing fields from different sources). ***FileDefinitionName*** Datasource name, enter a unique name for the file definition. ***File Path*** The default file path to automatically load file fields from an existing csv file ***File Fields*** Define a collection of fields in the file (when creating the metadata, this collection is empty and will be generated from the file and separator specified in the File Path and Field Separator properties. ***Field Separator*** Define the field separator character --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.appstrategy.com/apprules-r-documentation/platform/platform-features/system-settings/data-sources/connection-settings/files/delimited-file.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.