Send an HTTP Request to SharePoint Compose-Type Error

[DanielGAJohnson]

Hi All,

I'm trying to follow this guide (https://sharepains.com/2020/11/03/rename-sharepoint-folder-power-automate/) to rename a folder as part of my flow, but the flow checker is sending up the following error:

"Correct to include a valid reference to '_Compose-_Type' for the input parameter(s) of action 'Send_an_HTTP_request_to_SharePoint'.

I assume it means I need to add another header where the key is Compose-Type, but what is the value meant to be? 

[abm]

Hi @DanielGAJohnson 

In that article I can see there is a GET operation step 'Send an HTTP request to SharePoint 2'

After that step there are two compose action steps called Compose - Type expression as
outputs('Send_an_HTTP_request_to_SharePoint_2')?['body/d/__metadata/type']

Next action step Compose - ETag expression

outputs('Send_an_HTTP_request_to_SharePoint_2')?['body/d/__metadata/etag']

You need to reference both the Compose outputs  in your next HTTP Post Step.

Thanks

[DanielGAJohnson]

Hey @abm , thanks for the reply! I think I've got that part figured out, although the article I'm working from is not entirely clear which compose output goes where. Any ideas?

Also, I've managed to stop this error by putting in the right compose step, however, I'm now getting another error. The flow is triggered when a new folder is created in SharePoint. New folders are created from an automation in our CRM connected to SharePoint. When a new project is created in the CRM, it creates a new project folder in SP. The CRM's automation engine isn't capable of creating subfolders though, so that's where Power Automate takes over. The flow copies project template folders, and then is meant to feed the link to those folders back into the CRM with an API call. All that works, however, in order to send the API call back to the CRM, it has to know which record to update with the new folder links. So, when the original project folder is created, I've appended the record ID to the name so that I could parse it out with a compose step. However, it leaves the folder name quite messy, so I wanted to rename the folder to just the project name. In the HTTP GET request step I originally tried to put in the full path created by the trigger, but was getting an error. Then, I just tried to manually enter the path like the person in that post did, and got this error:

The expression "web/GetFolderByServerRelativeUrl('/Shared Documents/Projects/Test Folder/DJ QB SP TEST 18" is not valid.
clientRequestId: 9b846b7c-0283-4294-ab01-87c7a0310112
serviceRequestId: 19dbe69f-d0c9-c000-51cf-eb87ccba46c3

Is it a syntax error? What am I missing??

[DanielGAJohnson]

I found this post saying there was an error with special characters (https://social.msdn.microsoft.com/Forums/en-US/e623fda1-805b-4b99-b329-8f10facdaae7/using-rest-api-g...). Indeed, my folder path would have a special character in it. I add the special character from the CRM automation so that I can base my parse step off that special character. I use the "#". Is there a safer character that would stop this error from happening, but would also pass the file/folder name test? It can't be any characters that Microsoft doesn't allow in their file/folder naming conventions, since the first step is the create a new folder.

[DanielGAJohnson]

I replaced the '#' with a text string not likely to come up organically and it worked.