Hi @Jun Ting Ho
The error is expected behavior as I see that you are using the source URL as Path of Get file metadata that returns BlobMetaData that has the Path which is The path of the file or folder of the onedrive.
As you can see that the Path returns the right value in your case i.e. sL4ALP-file.txt
but the Copy File accepts its as Source URL which is incorrect as the file name is passed. The copy File action needs the publicly accessible URL or the file share that you have configured so it can get the content and write the content to your destination path specified. I don't see any option to get the direct downloaded URL for the onedrive file that you can pass to the Copy File action. We do have the Create Share link connector that have SharingLink as output but your onedrive/organization should allow the publicly access URL. Once you have shared link then you can offload the functionality to azure function/your own logic to get the direct link and pass it to your Copy File action.
Alternative as you are using Get File Content action you can pass the output to Create file action of azure file. Please review the limitation of the connectors.
Feel free to get back to me if you have any queries or concerns.
He tried to use the link direct from OneDrive:
Still same error message:
Raw output of error:
(Cont in next because of length)
(Raw output of error message from using OneDrive direct link ends here)
As you can see in the updated question, he has tried using "Create file", but he cannot select anything in "Folder path". How does he resolve this?
@Mark JZ Yeap There was typo and I mean to say "Create Share link connector that have SharingLink as output". The above error is expected as I mentioned in my answer as your organization doesn't allow you to create the
Anonymous
link scope for this option would not be possible for you.For the error "File name is null or empty" it is because you have not specified the file share name. In the Destination file path it should be "yourfileseverpath/copy-test-2.txt".
Once you fix the above issue then you will get 403 error (authentication issue) as your sharepoint path is not Anonymous accessible as mentioned previously.
The best way would be using Get File Content action you can pass the output to Create file action of azure file as mentioned in my answer.
@Mark JZ Yeap The same I have mentioned in your query here.
Please let me know if you need any assistance and we can connect offline.
Hi Sir,
What about the "Folder path" showing "No items" when I try to use "Create file" with the Azure File Storage connector, as shown in the screenshot in the updated question? How can I resolve this issue?
@Jun Ting Ho Please navigate to your storage account which you have configured in your connection. Navigate to File share and verify whether there is any file share created for you.
In scenario where there are no file share created you will see "No items" as you have observed. Please create the file share and confirm if you are still facing the issue.
Yes, Sir, that was the missing step. After creating file share and using it as folder path, the Create file was successful and I can see the created file. Thank you very much.
@Jun Ting Ho Thanks for the confirmation. Glad to know that the issue is resolved now.
@Mark JZ Yeap I believe this query was also related to this issue. Feel free to 'Accept as Answer' on your other post so it can help others in the community looking for help on similar topics.
You're welcome.
Sign in to comment
0 additional answers
Sort by: Most helpful