Delete a file from OneDrive for Business in for each loop in Logic Apps gives an error - onedrive

When I create a Logic App, I'm listing the file content in one drive for business. Then, I'm creating a ForEach to loop through the files in a folder and delete them. The system is not deleting the files and giving a 404 error.
I do the same example for copy, it works fine. The same example works fine if I replace the oneDrive for business adaptor with SFTP for example.
I've attached files for the design I've done and the error I get:
LogicApp Workflow
404 Error

Delete file API by OneDrive takes an ID rather than the file path. So in your case, specify "Id" token and it should work.

Related

Unable to list folders when using scoped app permission for Dropbox

I'm able to successfully list folder and contents when my dropbox developer app has full access, however, when I'm using scoped access only to a specific folder, it fails.
Now when I switch to scoped access to a specific folder I'm running into errors. This request should fail since the app does not have access to the folder.
Now when I put in the right folder path, I'm still getting the same error.
For reference I'm sharing my app details
It looks like you're using the App Folder permission. This will root all your paths relative to that app folder; your app will not be able to see outside of it.
For example, if the user sees the file as "/Apps/AppFolderAccess/myfile.txt", your app will see it as "/myfile.txt". By setting your path to /Apps/AppFolderAccess, it is effectively resolving as /Apps/AppFolderAccess/Apps/AppFolderAccess - which is not found.
If your application needs to see content outside its app folder, you should select full access.
Building on top of the other answer: you need to set the application permission to access type "Full Dropbox– Access to all files and folders in a user's Dropbox."
However, note that this requires you to delete your existing app and create a new one since it is not possible to change the scope of an existing app.

Browser cannot download .txt file if the project is .Net Core Restful API

I am trying to activate my SSL for my project but one of the the urls doesn't respond.
This is the web site and when you paste the url to the browser, it downloads the .txt file.
http://www.xxx.co.uk/.well-known/pki-validation/83CB00D29E282E1FFD6DFB220F030EF4.txt
This is the Restful .Net Core API domain and when you paste the url to the browser, it returns 404 error.
http://api.xxx.co.uk/.well-known/pki-validation/83CB00D29E282E1FFD6DFB220F030EF4.txt
Under the IIS I have compared the psychical paths, permissions and it seems everything is same. I believe something in Rest API blocks the .txt file download. Should I check the web.config or something I need to add to the C# source code? Should I update ConfigureServices(IServiceCollection services)? In IIS I have checked MIME Types and the .txt is already defined.
Any suggestions?
I believe my problem is pointing to this subject but I am not sure how to enable/define .txt files in startup.cs. Any code snippets?
How to Serve Static File
EDIT: Finally I found a solution. Now the browser can download the .txt files. What I did is, I created a virtual directory in IIS. Here are the steps:
Go to the C: drive
Create a new folder called well-known
Inside the .well-known folder, create another folder named pki-validation
so far, your folders should look like this: C:\.well-known\pki-validation
Upload the TXT file in the pki-validation folder
Open the IIS Manager on your server
Do a right click on your website and select Add Virtual Directory
In the Alias section write .well-known
In the Psychical Path area enter the path to the well known folder. For example: C:\well-known
Press OK to create this alias
The urls are now serving the .txt files. I hope these steps one day saves the other developers time.

Flow not displaying onedrive for business files

I am trying to create a flow that links files on my company's onedrive for business account with our SharePoint site. The first time I tried this, when I clicked the bar beside "*Folder", it listed the folders on my onedrive account and I was able to select the one wanted to create the flow between.
View Creating Flow:
However. A week later, I resolved an unrelated issue with the process and tried to create a new flow, but now, when I try to click the bar, this is all I get. Root is not a file on my onedrive, and it doesn't expand into anything. I have tried, putting in, "/File Name", but it won't recognize the file name, and the flow fails when I test it. I am not sure what I am doing differently this time that is causing Flow not to recognize the onedrive folders.
There is no folder, "root" in my one drive, and root doesn't expand into anything:
Root means the primary (main) OneDrive folder. If you click on the > next to root, it will open up the primary OneDrive folder and list all of the subfolders, as well as, all of the documents in the root folder.

ECM Sitecore Upload Receipts From .CSV Error

Has anyone received the following error when trying to upload receipts in Sitecore Email Campaign Manager? It looks like the file is not being saved in the temp folder. The error is not consistent. It happens sporadically.
Ensure the temp folder has Network Service write permissions on it.
Also ensure these steps have been done:
1) Change the Identity in Application Pool as Network Service
2) Make sure that the website folder and all its descendants and the data folder and all its descendants have read and write access for Network Service.

Display list files and folder using Mediafire API

I tryed to use Mediafire API, but when I use Folder, get_info, it doesn't return file & folder array like the example.
Full url I used: http://www.mediafire.com/api/folder/get_info.php?folder_key=l461cm2d8hfxd
What's wrong with my attempt? Thank you.
You can try the MediaFire API PHP Library. This class currently implements all the functions in the Mediafire API.
Ok I just took a look at their API documentation. They've updated the get_info function for the folders. They've taken out the file tree....
So if you are uploading via the dropbox (which doesn't return the quickkey associated with the file), you CAN NEVER dropbox upload and then use the api to find the file and download it. This renders their API as useless as tits on a boar hog.
The point of a dropbox is to allow remote uploads to a folder, you then know the folder key so you can query the API and return the document quickkeys that are in the folder which then allows you to manage those files remotely, move, delete, download etc. Now you cannot do this FAIL FAIL FAIL.
Despite the Functionality of get_info not working, folder search can resolve at least some issues with retrieving quick keys. In my case i searched for ".mp3" and was handed all the mp3s in my folder