Usage of OneDrive Connector in ETL pipeline
Last updated
Last updated
To use OneDrive connector in the ETL pipeline, the file details can be provided in multiple ways both in the Reader and the Writer.
To read data from OneDrive, users have the following options to provide details about the source file.
Path of File: XXX
File name: testonedrive.csv
Path of File: folder URL
Right click the folder>Share.
Click Copy.
Copy link.
File name: name of file.
Path of File: folder path (example: folder1/folder2/folder3/)
File name: name of file
Path of File: File Path (File URL generated by right-click on file>select Preview)
Path of File: file URL
Right click the file>Share.
Click Copy.
Copy link.
File name: empty.
Path of File: file path (example: folder1/folder2/file1.csv),
File name: empty
Shared files/folders are available to the OneDrive connector.
In order to access shared files/folders, the links, URLs, or Folder/file paths can be given as per in the earlier scenarios with the exception that when we are using paths (not URLs), the path must start with "/shared".
Note: If a user has a folder named "shared" in this root and they try to access it with the path (like /shared/...), it will not work because the connector will assume that it should be searching for shared files/folders. The way to work around this is to start the path with "my files". Therefore the path will look like "/my files/shared/...". The text 'my files' can always be used at the beginning of the path when pointing to the user's drive, however it is not necessary.
In case the file path is known, however, there is no destination file, provide the file (folder) path. On running the ETL, a file will be created labelled as “temp_(generated GUID number)”.
