> For the complete documentation index, see [llms.txt](https://docs.frends.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frends.com/tasks/tasks/azure-data-lake/uploadfiles.md). # UploadFiles Task version: 1.4.0 Required Frends version: 5.5+ Required .NET version: 6.0 Compatible Agents: Crossplatform Source code: ## Task Parameters {% tabs %} {% tab title="Input" %} | Name | Description | | ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Source : `Source` |

Specify source files parameters


Default: -
Example: -

| | Destination : `Destination` |

Specify destination Data Lake parameters


Default: -
Example: -

| | Options : `Options` |

Specify options how we should handle data and errors


Default: -
Example: -

| | Overwrite : `Boolean` |

How the existing file will be handled.


Default: False
Example: true

| | UploadFilesRecursively : `Boolean` |

True: Upload all files matching pattern, even in nested directories.

False: Upload files matching pattern, which are only directly in Source Directory


Default: True
Example: true

| | Close : `Boolean` |

Specifies whether the uploaded file should be finalized (closed) after upload.

When true, it triggers a "final update" event in Azure Storage Events.


Default: True
Example: true

| | {% endtab %} | | | {% endtabs %} | | ## Task Result | Name | Description | | ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Success : `Boolean` |

Operation complete. Returns false if ThrowErrorOnFailure is disabled and error occurred. Returns true otherwise.
Example: true

| | Data : `Dictionary` |

This object contains the list of local source file paths and their respective URLs in Azure Data Lake. If an ignorable error occurs, such as when a file already exists and Options.ThrowErrorOnFailure is set to false, the URL will be replaced with the corresponding error message.age.
Example: { { c:\temp\examplefile.txt, }, { c:\temp\examplefile2.txt, File examplefile2 already exists. } }

| | ErrorMessage : `String` |

This object contains the error message if task fail.
Example: Container ex does not exist

| ## Task Changelog Changelog for Task Frends.AzureDataLake.UploadFiles. ### \[1.4.0] - 2026-01-15 #### Changed * Updated Azure packages to latest versions: * Azure.Storage.Files.DataLake 12.25.0 * Azure.Identity 1.17.1 ### \[1.3.0] - 2025-05-07 #### Added * Added new Close parameter to control whether the uploaded file is finalized after upload. * Use the default parameter value ('true') if you want the upload operation to work as before (automatically closing the stream). * Set to 'false' if you need to manage the stream lifecycle manually after upload. ### \[1.2.0] - 2024-08-23 #### Changed * Updated the Azure.Identity package to version 1.12.0. ### \[1.1.0] - 2024-05-20 #### Added * Added FrendsTaskMetadata.json ### \[1.0.0] - 2024-05-14 #### Added * Initial implementation of Frends.AzureDataLake.UploadFiles. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.frends.com/tasks/tasks/azure-data-lake/uploadfiles.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.