Power Platform Community Forum Thread Details

Flow is connected to Power App custom connector. Power App initiates custom connector. Custom connector passes data (image, file name) to Flow and then Flow passes data to SPO.

http request - In the past I left scheme blank and my Flow functioned until Saturday 31st May . Today 3rd of June it failed when it reached the second step my 'trigger expression. ' I added the below Json but this failed.

{
 "type": "object",
 "properties": {
 "address": {
 "type": "string"
 }
 },
 "required": [
 "address"
 ]
}

Second step, my trigger espression. This trigger expression grabs the file name. Interestingly without the outputs, queries, filename just trigger() the output in the past would list the 'body' sent file from Postman. Now it fails to do so.

trigger()['outputs']['queries']['filename']

Third trigger expression.

triggerMultipartBody(0)['$content']

Error:

Unable to process template language expressions in action 'Get_File' inputs at line '1' and column '1812': 'The template language function 'triggerMultipartBody' failed to retrieve multipart contents from outputs. The supported multipart content type is 'multipart/*' and the provided content type is '<null>'. '.

Any suggestions to resolve this.

Thank you.

Categories:

General topics

Hello @Brad_Groux

Thank you for taking the time to respond. I appreciate you doing so. As requested I provided Flow details and a One Drive shareed links zip file of screen capture images.

Http request/response trigger.
Add Compose Action, Data Operations
1. Inputs - trigger()['outputs']['queries']['filename']
Create flow (save), Open http request/response and copy the URL.
Open Postman select Post and paste URL.
Add ‘&param=test’ to the end of the URL and click send.
Postman ‘status 202 Accepted.’
Flow trigger Inputs

{
 "name": "manual",
 "inputs": {
 "schema": {
 "type": "object",
 "properties": {
 "address": {
 "type": "string"
 }
 },
 "required": [
 "address"
 ]
 }
 },
 "outputs": {
 "headers": {
 "Cache-Control": "no-cache",
 "Connection": "keep-alive",
 "Accept": "*/*",
 "Accept-Encoding": "gzip,deflate",
 "Host": "prod-34.westeurope.logic.azure.com:443",
 "User-Agent": "PostmanRuntime/7.13.0",
 "Postman-Token": "9aea7073-dce1-4acb-a7d8-46ea90ad3f9d",
 "Content-Length": "0"
 },
 "queries": {
 "param": "test"
 }
 },
 "startTime": "2019-06-04T08:28:25.2307373Z",
 "endTime": "2019-06-04T08:28:25.2307373Z",
 "trackingId": "79cb6876-4c7f-475c-b72a-22c247c46572",
 "clientTrackingId": "08586419699802410804933421203CU102",
 "originHistoryName": "08586419699802410804933421203CU102",
 "status": "Succeeded"
}

8. Flow trigger Outputs

{
 "name": "manual",
 "inputs": {
 "schema": {
 "type": "object",
 "properties": {
 "address": {
 "type": "string"
 }
 },
 "required": [
 "address"
 ]
 }
 },
 "outputs": {
 "headers": {
 "Cache-Control": "no-cache",
 "Connection": "keep-alive",
 "Accept": "*/*",
 "Accept-Encoding": "gzip,deflate",
 "Host": "prod-34.westeurope.logic.azure.com:443",
 "User-Agent": "PostmanRuntime/7.13.0",
 "Postman-Token": "9aea7073-dce1-4acb-a7d8-46ea90ad3f9d",
 "Content-Length": "0"
 },
 "queries": {
 "param": "test"
 }
 },
 "startTime": "2019-06-04T08:28:25.2307373Z",
 "endTime": "2019-06-04T08:28:25.2307373Z",
 "trackingId": "79cb6876-4c7f-475c-b72a-22c247c46572",
 "clientTrackingId": "08586419699802410804933421203CU102",
 "originHistoryName": "08586419699802410804933421203CU102",
 "status": "Succeeded"
}

9. Return to Postman. Edit the body and select form data and I select file then add file.

10. Postman ‘status 202 Accepted.’

11. Flow trigger Input

{
 "name": "manual",
 "inputs": {
 "schema": {
 "type": "object",
 "properties": {
 "address": {
 "type": "string"
 }
 },
 "required": [
 "address"
 ]
 }
 },
 "outputs": {
 "headers": {
 "Cache-Control": "no-cache",
 "Connection": "keep-alive",
 "Accept": "*/*",
 "Accept-Encoding": "gzip,deflate",
 "Host": "prod-34.westeurope.logic.azure.com:443",
 "User-Agent": "PostmanRuntime/7.13.0",
 "Postman-Token": "743f1915-e79c-4e66-a481-2937bff116be",
 "Content-Length": "0"
 },
 "queries": {
 "param": "test"
 }
 },
 "startTime": "2019-06-04T08:33:43.4657084Z",
 "endTime": "2019-06-04T08:33:43.4657084Z",
 "trackingId": "bae05838-6b1d-45a2-a6d7-ad138a0af532",
 "clientTrackingId": "08586419696619992512557303299CU33",
 "originHistoryName": "08586419696619992512557303299CU33",
 "status": "Succeeded"
}

12. Flow trigger Output

{
 "name": "manual",
 "inputs": {
 "schema": {
 "type": "object",
 "properties": {
 "address": {
 "type": "string"
 }
 },
 "required": [
 "address"
 ]
 }
 },
 "outputs": {
 "headers": {
 "Cache-Control": "no-cache",
 "Connection": "keep-alive",
 "Accept": "*/*",
 "Accept-Encoding": "gzip,deflate",
 "Host": "prod-34.westeurope.logic.azure.com:443",
 "User-Agent": "PostmanRuntime/7.13.0",
 "Postman-Token": "743f1915-e79c-4e66-a481-2937bff116be",
 "Content-Length": "0"
 },
 "queries": {
 "param": "test"
 }
 },
 "startTime": "2019-06-04T08:33:43.4657084Z",
 "endTime": "2019-06-04T08:33:43.4657084Z",
 "trackingId": "bae05838-6b1d-45a2-a6d7-ad138a0af532",
 "clientTrackingId": "08586419696619992512557303299CU33",
 "originHistoryName": "08586419696619992512557303299CU33",
 "status": "Succeeded"
}

13 Note: Output has no ‘body’ below the OUTPUT queries entry. In the past you would have the following example below queries:

“body”:
{
“content-type”:multipart/form-data;boundary=----------------------------------------
6777884455221837”,
“content”:
“LSOtlSOtlQUNEDFEGNOCMELL
“multipart”: [
{
	“headers”:{
“Content-Description”:”form-data; name=\”\”;filename=\Filezilla.png\””,
},
“body”:{
“content-type”:”image/jpeg”,
“$content”: 
“aVXTFKLTPONNFFLLOPPPP
}
}
]
},
“startTime”:”2019-05-30:0945:55.9237442Z”’
“endtime”: ”2019-05-30:0945:55.9237442Z”’
“trickingId”:”12f78986-4951-b2f0”,
“clientTrackingId:”:”08452134647333”,
“status”:”succeeded”
}

ALL the above is missing

13. In my view the reason the Flow fails is due to the trigger missing the body entry.

14. Returning to Postman, I’ll remove ‘param=test from the URL and type filename=123.jpg. I’ll click send and return to Flow.

15. Expanding the Flow, Compose output I see the following:

{
 "name": "manual",
 "inputs": {
 "schema": {
 "type": "object",
 "properties": {
 "address": {
 "type": "string"
 }
 },
 "required": [
 "address"
 ]
 }
 },
 "outputs": {
 "headers": {
 "Cache-Control": "no-cache",
 "Connection": "keep-alive",
 "Accept": "*/*",
 "Accept-Encoding": "gzip,deflate",
 "Host": "prod-34.westeurope.logic.azure.com:443",
 "User-Agent": "PostmanRuntime/7.13.0",
 "Postman-Token": "8d2373b2-f3b2-4c43-9d97-a43e58cee7c2",
 "Content-Length": "0"
 },
 "queries": {
 "filename": "123.jpg"
 }
 },
 "startTime": "2019-06-04T09:02:45.0501887Z",
 "endTime": "2019-06-04T09:02:45.0501887Z",
 "trackingId": "937503ae-0894-4d80-98f4-47aac71e2209",
 "clientTrackingId": "08586419679204120907049440274CU14",
 "originHistoryName": "08586419679204120907049440274CU14",
 "status": "Succeeded"
}

17. Note: Below “queries” “body” is missing. In fact, everything related to the file no encoding AT ALL.

18. Assuming the body is present. I would make the trigger more targeted by reformulating my trigger to ‘trigger()['outputs']['queries']['filename'].’

19. Expanding the Flow, Compose output I see the following:

Input = filename=123.jpg

Output = filename=123.jpg

20. Regrettably despite the ability to successfully exact the file name the file coding isn’t present so the second compose data connection trigger fails.

21. Assuming the above worked I would add another compose data connection and add the following trigger expression. triggerMultipartBody(0)['$content']. My objective is I want the file content.

22. I return to Postman, change the filename and change the file and click send.

23. Return to Flow and expand flow to identify the error message. Reads as follows:

Unable to process template language expressions in action 'Get_File' inputs at line '1' and column '1811': 'The template language function 'triggerMultipartBody' failed to retrieve multipart contents from outputs. The supported multipart content type is 'multipart/*' and the provided content type is '<null>'. '.

Failure isn’t surprising given the malfunction to extract the Body in the first compose data connection trigger. Assuming the trigger worked I would amend the trigger to base64ToBinary(triggermultipartbody(0)['$content']) finally I would had another action adding SharePoint connector create file. I'd configure the site and document library then link file name to file name compose trigger output and file content trigger output to get filecontent.

Screen capture images One Drive https://1drv.ms/u/s!Ak789NvNyMQ3oohVdcEZf7zc49EY5g?e=GHhERc